Triple
T25913401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridge Pavilion, Zaragoza |
E652960
|
entity |
| Predicate | functionDuringExpo |
P47533
|
FINISHED |
| Object | entrance to Expo 2008 site |
—
|
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: entrance to Expo 2008 site | Statement: [Bridge Pavilion, Zaragoza, functionDuringExpo, entrance to Expo 2008 site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionDuringExpo Context triple: [Bridge Pavilion, Zaragoza, functionDuringExpo, entrance to Expo 2008 site]
-
A.
functionDuringEvent
chosen
Indicates that a particular function, role, or operation is active or carried out during a specified event.
-
B.
functionDuringPeriod
Indicates that a function, role, or activity is performed or valid throughout a specified time period.
-
C.
functionDuringEdoPeriod
Indicates that the function, role, or activity occurred specifically during Japan’s Edo period.
-
D.
operatorDuringExpo
Indicates that an entity serves as an operator specifically during an exposition or expo event.
-
E.
hasExpo
Indicates that an entity hosts, participates in, or is associated with an exposition or exhibition event.
- 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_69e7ab3e025c819086771607157f0015 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 22, 2026, 8:30 a.m.