Triple
T37251591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michel Delving |
E924007
|
entity |
| Predicate | officeHeldThere |
P25590
|
FINISHED |
| Object | Mayor of the Shire |
—
|
LITERAL 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: Mayor of the Shire | Statement: [Michel Delving, officeHeldThere, Mayor of the Shire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeHeldThere Context triple: [Michel Delving, officeHeldThere, Mayor of the Shire]
-
A.
officeHeldIn
chosen
Indicates that a particular office or position is held within or associated with a specific geographic or administrative location.
-
B.
officeHeldDuring
Indicates that a person occupied a specific official position during a particular time period.
-
C.
officeHeldOf
Indicates that a specific office or position is (or was) held by a particular person or entity.
-
D.
officeHeldUnder
Indicates that one entity holds or has held an official position, role, or office under the authority, jurisdiction, or administration of another entity.
-
E.
aboutOfficeHeld
Indicates that one entity is related to, or provides information about, a specific office or position that is or was held by another entity.
- 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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a004b6ad4248190b402a0d01b0ebf83 |
completed | May 10, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a004ae736b881908a0efed8f63f982e |
completed | May 10, 2026, 9:07 a.m. |
Created at: May 3, 2026, 4:15 p.m.