Triple
T14899935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carl Sagan |
E359976
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Sagan |
E359976
|
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: Sagan | Statement: [Carl Sagan, familyName, Sagan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sagan Context triple: [Carl Sagan, familyName, Sagan]
-
A.
Sagan
chosen
Sagan is a surname most famously associated with astronomer and science communicator Carl Sagan and his family.
-
B.
Sagan
Sagan is a town in present-day Żagań, Poland, historically known as a center where the astronomer Johannes Kepler conducted part of his scientific work.
-
C.
Niven
Niven is a Scottish-origin surname most famously associated with the English actor David Niven.
-
D.
Silloo Bode
Silloo Bode was the wife of Indian Field Marshal Sam Manekshaw and a member of the Parsi community.
-
E.
Bardeen
Bardeen is a surname most notably associated with John Bardeen, the American physicist who won the Nobel Prize in Physics twice for his work on the transistor and superconductivity.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded609bf68819099ca3aa3fe1acadc |
completed | April 15, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe6b6a8aac8190ad062b80d384fb14 |
completed | May 8, 2026, 11:02 p.m. |
Created at: April 10, 2026, 2:11 a.m.