Triple
T11041246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argonaut Mine |
E261020
|
entity |
| Predicate | eraOfMajorOperation |
P97447
|
FINISHED |
| Object | late 19th century |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: late 19th century | Statement: [Argonaut Mine, eraOfMajorOperation, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfMajorOperation Context triple: [Argonaut Mine, eraOfMajorOperation, late 19th century]
-
A.
eraOfOperation
Indicates the time period or span of years during which an entity was active or in operation.
-
B.
majorOperation
Indicates that one entity performs or undergoes a significant, large-scale, or primary operation or procedure involving another entity or context.
-
C.
majorOperationsOf
Indicates that one entity is a primary or significant operation, activity, or functional undertaking associated with another entity.
-
D.
eraOfMajorConstruction
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
E.
hadMajorOperationsIn
Indicates that an entity has undergone significant or primary operations or activities in a specified location or context.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7980050948190ae7b187da5b776ca |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.