Triple
T31018454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Dallas |
E790387
|
entity |
| Predicate | scriptDesignation |
P505
|
FINISHED |
| Object | Dallas |
—
|
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: Dallas | Statement: [Captain Dallas, scriptDesignation, Dallas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptDesignation Context triple: [Captain Dallas, scriptDesignation, Dallas]
-
A.
systemDesignation
Indicates that an entity has been assigned a specific formal label or identifier within a defined system or framework.
-
B.
script
chosen
Indicates that an entity is associated with a written text or code (such as a screenplay, program, or written instructions) that defines its content or behavior.
-
C.
scriptDescription
Indicates that a script provides a textual explanation or summary describing its content, purpose, or behavior.
-
D.
editorialDesignation
Indicates that an entity has been assigned a specific editorial label or status within a publication or editorial workflow.
-
E.
programDesignation
Indicates that an entity is assigned or identified by a specific program designation or label.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 29, 2026, 8:58 p.m.