Triple
T31593907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highball |
E806170
|
entity |
| Predicate | projectCodeName |
P172872
|
FINISHED |
| Object | Highball |
—
|
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: Highball | Statement: [Highball, projectCodeName, Highball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectCodeName Context triple: [Highball, projectCodeName, Highball]
-
A.
testCodeName
Indicates that an entity is identified or referred to by a specific test code name.
-
B.
projectNameVariant
Indicates that one project name is an alternative or variant form of another project name.
-
C.
productionCode
Indicates the unique identifier or code assigned to a specific production (such as a film, TV episode, or manufactured item) that links related records or versions of that production.
-
D.
projectNumber
Indicates a relationship where a specific identifying number is assigned to or associated with a particular project.
-
E.
projectModel
Indicates a relationship where one entity serves as a model, template, or representation for a project or projected outcome involving another entity.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 30, 2026, 10:29 p.m.