Triple
T2424944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expo 85 |
E53503
|
entity |
| Predicate | exhibitedTechnology |
P35733
|
FINISHED |
| Object | robotics |
—
|
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: robotics | Statement: [Expo 85, exhibitedTechnology, robotics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exhibitedTechnology Context triple: [Expo 85, exhibitedTechnology, robotics]
-
A.
hasTechnologyDemonstration
chosen
Indicates that an entity includes, features, or is associated with a demonstration of a particular technology or technological capability.
-
B.
exhibitedWith
Indicates that two or more entities were presented or displayed together as part of the same exhibition or show.
-
C.
offeredTechnology
Indicates that one entity has provided or proposed a specific technology to another entity as an option for use, adoption, or consideration.
-
D.
hasInteractiveExhibits
Indicates that something contains exhibits designed for active participation or engagement by the audience.
-
E.
laterUsedTechnology
Indicates that one entity adopted or employed a technology after another entity had already used it.
- 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.