Triple
T360126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Tavern site |
E7831
|
entity |
| Predicate | originalBuildingConstructed |
P12341
|
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: [City Tavern site, originalBuildingConstructed, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBuildingConstructed Context triple: [City Tavern site, originalBuildingConstructed, 18th century]
-
A.
castleBuiltFor
Indicates that a castle was constructed specifically for the benefit, use, or commission of a particular person, group, or purpose.
-
B.
building
Indicates that one entity constructs, assembles, or develops another entity, typically over a period of time.
-
C.
builtProperty
Indicates that a constructed structure or building has been created on, or is associated with, a particular property or piece of land.
-
D.
significantBuilding
Indicates that a building holds notable importance, prominence, or special status within a particular context (e.g., historical, cultural, architectural, or functional).
-
E.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebccb8d88190a31f7c443a0c8566 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95aeed48190b5e48865cc964938 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea2c44408190946267525c88e811 |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.