Triple
T38285440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Pavilion |
E1022193
|
entity |
| Predicate | originalBuildingErected |
P12341
|
FINISHED |
| Object | 1753 |
—
|
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: 1753 | Statement: [Chinese Pavilion, originalBuildingErected, 1753]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBuildingErected Context triple: [Chinese Pavilion, originalBuildingErected, 1753]
-
A.
originalBuildingConstructed
chosen
Indicates that a particular building was initially constructed in its original form or configuration.
-
B.
originalBuilding
Indicates that a building is the initial or first version from which later buildings, modifications, or replacements are derived.
-
C.
originalBuildingName
Indicates that a building’s referenced name is its original or historically first assigned name, as opposed to any later or alternate names.
-
D.
originallyErectedIn
Indicates that something was first constructed or put up in a specific place or location.
-
E.
originalBuildingType
Indicates the type or category of building that something was initially constructed or designated to be, before any later changes or repurposing.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.