Triple
T1668317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brendan |
E36062
|
entity |
| Predicate | relatedName |
P3889
|
FINISHED |
| Object | Brandon |
E151225
|
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: Brandon | Statement: [Brendan, relatedName, Brandon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brandon Context triple: [Brendan, relatedName, Brandon]
-
A.
Brandon
chosen
Brandon is a masculine given name of Old English origin meaning "hill covered with broom" or "beacon hill."
-
B.
Brandon
Brandon is a town in Suffolk, England, known for its location on the Breckland railway line and its surrounding Breckland heathland and forestry.
-
C.
Bryan
Bryan is a masculine given name of Celtic origin that is widely used in English-speaking countries.
-
D.
Wayne
Wayne is a suburban community in Pennsylvania’s Main Line region, known for its residential neighborhoods and commuter access to Philadelphia.
-
E.
Wayne
Wayne is a masculine given name of English origin commonly used in the United States and other English-speaking countries.
- 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_69a8861286808190939afff3ce8ee31e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa62d1261481909a01c8fe4ff7500d |
completed | March 6, 2026, 5:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad7988bda081908a966ae1f589cb8f |
completed | March 8, 2026, 1:28 p.m. |
Created at: March 4, 2026, 7:29 p.m.