Triple
T6553628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byron Mann |
E152388
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Mann |
E42631
|
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: Mann | Statement: [Byron Mann, familyName, Mann]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mann Context triple: [Byron Mann, familyName, Mann]
-
A.
Mann
chosen
Mann is a common German surname borne by numerous notable figures in literature, politics, and the arts.
-
B.
Mies
Mies is a small Swiss municipality in the canton of Vaud, located along Lake Geneva near the city of Geneva.
-
C.
Man
Man was a prominent British anthropological journal that served as the main publication of the Royal Anthropological Institute before being continued under a new title.
-
D.
Männiku
Männiku is a residential subdistrict of the Nõmme district in Tallinn, Estonia, known for its forests, sand quarries, and military training areas.
-
E.
MAN
MAN is the three-letter IATA airport code for Manchester Airport, a major international airport serving the Greater Manchester area in England.
- 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_69c688058d6881908c19b309cc55dbfa |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ae0847d88190b38f9d7dba0faae1 |
completed | March 27, 2026, 4:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6cb8041d081909cd64dab7ccbd035 |
completed | March 27, 2026, 6:25 p.m. |
Created at: March 27, 2026, 1:51 p.m.