Triple
T1202586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM Motorama |
E25815
|
entity |
| Predicate | includedElement |
P11236
|
FINISHED |
| Object | live entertainment |
—
|
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: live entertainment | Statement: [GM Motorama, includedElement, live entertainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedElement Context triple: [GM Motorama, includedElement, live entertainment]
-
A.
includesElement
chosen
Indicates that one collection, set, or structure contains a specified element as a member or component.
-
B.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
C.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
D.
usesElement
Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
-
E.
includesClause
Indicates that one entity (typically a document, contract, or statement) contains or incorporates a specific clause as part of its content.
- 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bdbda0b081909c0147121a945e27 |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5ed2b88190aab992913957e1cf |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.