Triple
T10971549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Max Irons |
E259246
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object | Condor |
E675154
|
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: Condor | Statement: [Max Irons, notableWork, Condor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Condor Context triple: [Max Irons, notableWork, Condor]
-
A.
Condor
Condor is a German leisure airline known for operating holiday flights to popular vacation destinations, primarily from bases in Germany.
-
B.
Condor
chosen
Condor is the codename of the CIA analyst protagonist in the political thriller novel and film "Three Days of the Condor."
-
C.
Condor
Condor is the nickname of the Focke-Wulf Fw 200, a long-range German airliner later used as a maritime patrol and bomber aircraft during World War II.
-
D.
Condors
Condors is the nickname of the Bakersfield Condors, a professional ice hockey team based in Bakersfield, California.
-
E.
Vultur
Vultur is a genus of large New World vultures best known for including the Andean condor, one of the world’s largest flying birds.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7719b5edc81908c1019f81e78bd2e |
completed | April 9, 2026, 9:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3743d16ac81909c2d4eb11713512b |
completed | April 18, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:24 p.m.