Triple
T6512196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mo Farah |
E150162
|
entity |
| Predicate | honorificPrefix |
P536
|
FINISHED |
| Object | Sir |
E20965
|
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: Sir | Statement: [Mo Farah, honorificPrefix, Sir]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sir Context triple: [Mo Farah, honorificPrefix, Sir]
-
A.
Sir
chosen
Sir is a formal English honorific title traditionally used to address or refer to a knight or baronet.
-
B.
SIR
SIR is the IATA airport code for Sion Airport, a regional airport serving the town of Sion in the Swiss canton of Valais.
-
C.
Sir Saint
Sir Saint is one of the New Orleans Saints’ official mascots, depicted as a mustachioed, medieval-style figure embodying the team’s namesake and spirit.
-
D.
Lord
A Lord is a noble title in the United Kingdom traditionally associated with membership in the peerage and, in many cases, a seat in the House of Lords.
-
E.
Lord
Lord is a reverential title for Jesus Christ, emphasizing his divine authority, sovereignty, and central role in Christian faith and worship.
- 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_69c687ef291081909d437f035eef1cda |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f3c5eb88190a56723acd8096dd8 |
completed | March 27, 2026, 3:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6cb6421748190b8f2b77c77b153bc |
completed | March 27, 2026, 6:24 p.m. |
Created at: March 27, 2026, 1:44 p.m.