Triple
T6842817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan |
E157814
|
entity |
| Predicate | hasCognate |
P2525
|
FINISHED |
| Object | John |
unclear NED1
|
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: John | Statement: [Ivan, hasCognate, John]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: John Context triple: [Ivan, hasCognate, John]
-
A.
John
John is the given name of John H. Hammond Jr., the influential American record producer and talent scout known for discovering and promoting numerous major jazz, blues, and rock musicians.
-
B.
John
John is the given name of John F. Sattler, likely referring to him in a more informal or abbreviated context.
-
C.
John
John is the given name of John Murray, 3rd Duke of Atholl, an 18th-century Scottish nobleman and peer.
-
D.
John
John is the given name of John Hersey, the American writer and journalist renowned for his groundbreaking reportage on the aftermath of the Hiroshima bombing.
-
E.
John
John is the given name of Sir John Borlase Warren, a prominent British naval officer and politician of the late 18th and early 19th centuries.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69c6882ed4c081909dc465a7cf8838be |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d6b5f7648190ad8561caeb678932 |
completed | March 27, 2026, 7:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c75115c74c81909b02e4c49a98663c |
completed | March 28, 2026, 3:55 a.m. |
Created at: March 27, 2026, 2:19 p.m.