Triple
T21519472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Munro Longyear |
E530934
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Longyear |
—
|
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: Longyear | Statement: [John Munro Longyear, familyName, Longyear]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Longyear Context triple: [John Munro Longyear, familyName, Longyear]
-
A.
Longyear
chosen
Longyear is a surname most notably associated with American politician and jurist John Wesley Longyear.
-
B.
Howden
Howden is a historic market town in the East Riding of Yorkshire, England, known for its medieval Minster and traditional town centre.
-
C.
Howden
Howden is a residential neighbourhood within the town of Livingston in West Lothian, Scotland.
-
D.
Nygaard
Nygaard is a Norwegian surname borne by various notable individuals in fields such as computer science, politics, and the arts.
-
E.
Reinholdt
Reinholdt is a masculine given name of Germanic origin, often associated with individuals from German-speaking regions.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee884af0f08190bc1f3d70e57a325d |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 16, 2026, 6:26 p.m.