Triple
T7582814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitol building (colonial) |
E179530
|
entity |
| Predicate | historicalEraRepresented |
P36399
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Capitol building (colonial), historicalEraRepresented, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEraRepresented Context triple: [Capitol building (colonial), historicalEraRepresented, 18th century]
-
A.
historicalEraOfNaming
Indicates the historical era or time period during which an entity received its name.
-
B.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
-
C.
historicalEraOfRise
Indicates the historical era or period during which an entity first rose to prominence, influence, or significance.
-
D.
historicalEraOfSuccess
Indicates that an entity achieved notable success or prominence during a specified historical era.
-
E.
representsEra
chosen
Indicates that one entity designates the historical era, period, or age to which another entity belongs or is associated.
- 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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9794034819088de196c3519a665 |
completed | March 27, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:52 p.m.