Triple
T33053963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Strike |
E845800
|
entity |
| Predicate | associatedProp |
P70956
|
FINISHED |
| Object | unadorned aluminum Festivus pole |
E235204
|
NE 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: unadorned aluminum Festivus pole | Statement: [The Strike, associatedProp, unadorned aluminum Festivus pole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedProp Context triple: [The Strike, associatedProp, unadorned aluminum Festivus pole]
-
A.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
B.
linkedToProperty
Indicates that one entity is associated or connected to a specific property or attribute of another entity.
-
C.
relatedAttribute
Indicates that one attribute is associated with, derived from, or otherwise contextually linked to another attribute.
-
D.
associatedItem
chosen
Indicates that one item is linked or connected to another in a relevant or context-dependent way, without specifying a more precise relationship.
-
E.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
- F. None of above.
Provenance (4 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34f01025208190a7cae6408f47afad |
completed | June 19, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:24 a.m.