Triple
T7518428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pair of Kings |
E177703
|
entity |
| Predicate | executiveProducer |
P7225
|
FINISHED |
| Object | Dan Cross |
E670400
|
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: Dan Cross | Statement: [Pair of Kings, executiveProducer, Dan Cross]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dan Cross Context triple: [Pair of Kings, executiveProducer, Dan Cross]
-
A.
Dan Cross
chosen
Dan Cross is a television writer and producer best known for co-creating the Disney XD comedy series "Pair of Kings."
-
B.
Dan Talbot
Dan Talbot was an influential American film distributor and exhibitor known for championing foreign and independent cinema in the United States.
-
C.
Larry Cross
Larry Cross is an actor known for his role in the film "Embassy."
-
D.
Ian Crafford
Ian Crafford is a film editor best known for his work on the James Bond movie "Never Say Never Again."
-
E.
John Crossley
John Crossley was a prominent British railway engineer who served as a leading figure in the development and management of the Midland Railway’s infrastructure.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c69f2891148190a484f3b8222c6f1b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5f850c081909e697219071293fc |
completed | March 27, 2026, 9:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c84ef834608190bf425f99222a4bc5 |
completed | March 28, 2026, 9:58 p.m. |
Created at: March 27, 2026, 3:46 p.m.