Triple
T28861058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piedmont Fox Hounds |
E728862
|
entity |
| Predicate | hasHuntStaffRole |
P108233
|
FINISHED |
| Object | Master of Foxhounds |
—
|
NE NERFINISHED |
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: Master of Foxhounds | Statement: [Piedmont Fox Hounds, hasHuntStaffRole, Master of Foxhounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHuntStaffRole Context triple: [Piedmont Fox Hounds, hasHuntStaffRole, Master of Foxhounds]
-
A.
hadStaffRole
chosen
Indicates that an entity served in a specific staff role or position for another entity during some period.
-
B.
hasAdultStaffRole
Indicates that an entity holds a staff position or role designated specifically for adults.
-
C.
hasLegalRole
Indicates that an entity holds a specific legal capacity, status, or function in relation to another entity or context.
-
D.
hasGlobalRole
Indicates that an entity holds a role or permission set that applies across an entire system or domain, rather than being limited to a specific scope or context.
-
E.
hasStageRole
Indicates that an entity performs or holds a specific role or character in a staged performance or theatrical production.
- F. None of above.
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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 6:47 a.m.