Triple
T4774127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copperopolis |
E106002
|
entity |
| Predicate | indicatesPastRoleAs |
P29914
|
FINISHED |
| Object | major center of copper smelting |
—
|
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: major center of copper smelting | Statement: [Copperopolis, indicatesPastRoleAs, major center of copper smelting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesPastRoleAs Context triple: [Copperopolis, indicatesPastRoleAs, major center of copper smelting]
-
A.
hasHistoricalRoleAs
chosen
Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or context.
-
B.
mayHavePriorRole
Indicates that an entity is allowed or expected to have held a specified role at some earlier time.
-
C.
servedInRole
Indicates that one entity performed duties or held a position within a specified role or office in relation to another entity.
-
D.
servedAs
Indicates that one entity held and performed the role, position, or function associated with another entity for some period of time.
-
E.
successorInSomeRoles
Indicates that one entity has taken over or followed another entity in certain specified roles or positions.
- F. None of above.
Provenance (3 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_69bd43f3074c8190937e7b0a457fe9f1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6560b3448190a0debbd8da29d986 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.