Triple
T35067664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trouble in Lumpy Space |
E1011773
|
entity |
| Predicate | airOrder |
P90018
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Trouble in Lumpy Space, airOrder, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airOrder Context triple: [Trouble in Lumpy Space, airOrder, 2]
-
A.
airingOrder
chosen
Indicates the sequence in which items (such as episodes or installments) are broadcast or released to the public.
-
B.
orderHead
Indicates that an entity serves as the primary or leading element in an ordered sequence or hierarchy.
-
C.
order
Indicates that one entity requests, arranges, or directs that another entity provide a good, service, or action, typically in a specified sequence or priority.
-
D.
orderHouse
Indicates that an entity requests or arranges the purchase or construction of a house.
-
E.
orderSystem
Indicates a relationship where one entity organizes, arranges, or structures another entity or set of entities into a coherent or regulated system.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78617d290819096712543cbb9d04e |
completed | May 3, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.