Triple
T11654529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yeoman |
E276983
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Yeoman |
E276983
|
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: Yeoman | Statement: [Yeoman, name, Yeoman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yeoman Context triple: [Yeoman, name, Yeoman]
-
A.
Yeoman
chosen
Yeoman is a scaffolding tool for modern web applications that streamlines project setup by generating boilerplate code and configuration through customizable generators.
-
B.
Yeomen and Yeowomen
Yeomen and Yeowomen are the athletic teams and mascots representing Oberlin College in intercollegiate sports.
-
C.
Exempt Yeomen
Exempt Yeomen are a select group within the British monarch’s ceremonial bodyguard, distinguished by their senior status and special duties.
-
D.
York Yeomen
York Yeomen was the former name of the varsity athletic teams representing York University in Toronto, Canada, before they were rebranded as the York Lions.
-
E.
Yeoman Bed Goer
Yeoman Bed Goer is a ceremonial position within the British monarch’s bodyguard, the Yeomen of the Guard, traditionally associated with duties related to the royal bedchamber.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3cee010819089cffdbefe5a6efb |
completed | April 10, 2026, 7:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ee88166900819095063f045be44bed |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 8, 2026, 9:39 p.m.