Triple
T31601767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Motors pavilion |
E806364
|
entity |
| Predicate | hasPostShow |
P88380
|
FINISHED |
| Object | GM showroom |
—
|
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: GM showroom | Statement: [General Motors pavilion, hasPostShow, GM showroom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostShow Context triple: [General Motors pavilion, hasPostShow, GM showroom]
-
A.
isPostShowFor
chosen
Indicates that one event, program, or segment occurs immediately after and is associated with a particular show (i.e., it is the follow-up or after-show for that show).
-
B.
hasFashionShow
Indicates that an entity organizes, hosts, or features a fashion show as an event or activity.
-
C.
hasPresented
Indicates that one entity has formally given, delivered, or shown something (such as information, a work, or an award) to another entity.
-
D.
hasPresentation
Indicates that an entity delivers, contains, or is associated with a specific presentation (such as a talk, slide deck, or formal display of information).
-
E.
performedOnShow
Indicates that an action or performance was carried out during or as part of a particular show or 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: April 30, 2026, 10:33 p.m.