Triple
T20425146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endon and Stanley |
E500978
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Endon |
—
|
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: Endon | Statement: [Endon and Stanley, contains, Endon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Endon Context triple: [Endon and Stanley, contains, Endon]
-
A.
Endon
chosen
Endon is a village in Staffordshire, England, known as the birthplace of early 20th-century poet and critic T. E. Hulme.
-
B.
Endore
Endore is a surname most notably associated with American novelist and screenwriter Guy Endore, known for his works in horror and historical fiction.
-
C.
Ende
Ende is a coastal town and regency capital on the Indonesian island of Flores, known as a regional hub and gateway to nearby natural attractions.
-
D.
Endo
Endo is an alternative name for the Marakwet people, an ethnic community primarily residing in Kenya’s Rift Valley region.
-
E.
Endo
Endo is a Japanese surname borne by numerous notable individuals across fields such as literature, sports, and entertainment.
- 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_69e0b4aa68fc8190b1a14c55575ef04a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67ba7afa4819095c9b75fab3cbbfc |
completed | April 20, 2026, 7:16 p.m. |
Created at: April 16, 2026, 11:30 a.m.