Triple
T15353154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brandon Trost |
E367103
|
entity |
| Predicate | givenName |
P17
|
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: [Brandon Trost, givenName, Brandon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brandon Context triple: [Brandon Trost, givenName, Brandon]
-
A.
Brandon
Brandon is a town in Suffolk, England, known for its location on the Breckland railway line and its surrounding Breckland heathland and forestry.
-
B.
Brandon
Brandon is a small city in eastern South Dakota that functions largely as a residential and commercial suburb of nearby Sioux Falls.
-
C.
Brandon
Brandon is a small historic town in Rutland County, Vermont, known for its classic New England charm and village center.
-
D.
Brandon
chosen
Brandon is a masculine given name of Old English origin meaning "hill covered with broom" or "beacon hill."
-
E.
Bron
Bron is a British actress and writer known for her work in film, television, and radio since the 1960s.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e2a8e88819093e4b7479b2c80cd |
completed | April 16, 2026, 1:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff01ff42d48190897e6653d2b4f8a4 |
completed | May 9, 2026, 9:44 a.m. |
Created at: April 10, 2026, 3:17 a.m.