Triple
T2424937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expo 85 |
E53503
|
entity |
| Predicate | mainGateFeature |
P31480
|
FINISHED |
| Object | large arch structure |
—
|
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: large arch structure | Statement: [Expo 85, mainGateFeature, large arch structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainGateFeature Context triple: [Expo 85, mainGateFeature, large arch structure]
-
A.
hasGate
Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
-
B.
gateWeight
Indicates the weight or importance assigned to a particular gate or transition within a process, model, or system.
-
C.
facadeFeature
chosen
Indicates that one element functions as a distinct architectural or design feature on the façade of another structure.
-
D.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
E.
hasFaregates
Indicates that an entity is equipped with or contains faregates used to control or validate access, typically for paid entry.
- 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_69ab495c44d48190b7235b23719bc3f6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc9f342e88190a430b02842ded418 |
completed | March 7, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69abc5a889948190b77de4ef6ac815a8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:42 p.m.