Triple
T12528729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquapolis floating city |
E299503
|
entity |
| Predicate | roleAtExpo |
P69200
|
FINISHED |
| Object | centerpiece pavilion |
—
|
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: centerpiece pavilion | Statement: [Aquapolis floating city, roleAtExpo, centerpiece pavilion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtExpo Context triple: [Aquapolis floating city, roleAtExpo, centerpiece pavilion]
-
A.
exhibitionRole
chosen
Indicates the specific function or capacity an entity has within the context of an exhibition (e.g., organizer, curator, exhibitor, or participant).
-
B.
exhibitorType
Indicates the specific role or category an exhibitor belongs to within an exhibition or event context.
-
C.
usedByExhibitorType
Indicates that something is utilized or applied by a specific type or category of exhibitor.
-
D.
ownerDuringExhibition
Indicates that an entity is the legal owner of another entity specifically for the duration of a particular exhibition or display period.
-
E.
organizerRole
Indicates that an entity has the role or responsibility of organizing an event, activity, or group.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.