Triple
T18411811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decumano axis |
E441775
|
entity |
| Predicate | hasVisitorFlowRole |
P102270
|
FINISHED |
| Object | primary circulation spine of Expo 2015 |
—
|
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: primary circulation spine of Expo 2015 | Statement: [Decumano axis, hasVisitorFlowRole, primary circulation spine of Expo 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitorFlowRole Context triple: [Decumano axis, hasVisitorFlowRole, primary circulation spine of Expo 2015]
-
A.
hasVisitorType
Indicates the type or category of visitor associated with an entity (e.g., guest, customer, tourist, patient).
-
B.
hasVisitorCharacteristic
Indicates that a visitor possesses or exhibits a particular characteristic, attribute, or quality.
-
C.
isMainVisitorHubOf
Indicates that a location serves as the primary central hub or focal point for visitors to a particular place, site, or area.
-
D.
hasEntranceRole
chosen
Indicates that an entity participates in an entrance or access point with a specific functional role or capacity.
-
E.
visitorIs
Indicates that one entity is acting in the role or capacity of a visitor with respect to another entity.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51a24e130819082b92f98d8d5fa3c |
completed | April 19, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.