Triple
T31352097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honky Grandma Be Trippin' |
E799623
|
entity |
| Predicate | inUniverseStar |
P180350
|
FINISHED |
| Object | Tracy Jordan |
—
|
NE NERFINISHED |
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: Tracy Jordan | Statement: [Honky Grandma Be Trippin', inUniverseStar, Tracy Jordan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseStar Context triple: [Honky Grandma Be Trippin', inUniverseStar, Tracy Jordan]
-
A.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
B.
inUniverseSystem
Indicates that one entity exists or operates within the scope, rules, or continuity of a particular fictional or conceptual universe or system.
-
C.
inUniversePlanet
Indicates that a planet exists within or belongs to a particular fictional or defined universe.
-
D.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
E.
eraInUniverse
Indicates the specific time period or era during which something exists or occurs within a particular fictional or defined universe.
- F. None of above. chosen
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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
| PDg | Predicate description generation | batch_69f73adfd9a081908adae6bd59dfefb9 |
completed | May 3, 2026, 12:09 p.m. |
Created at: April 29, 2026, 9:17 p.m.