Triple
T28974505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rangers of Ithilien |
E734371
|
entity |
| Predicate | governmentLoyalty |
P198104
|
FINISHED |
| Object | Steward of Gondor |
—
|
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: Steward of Gondor | Statement: [Rangers of Ithilien, governmentLoyalty, Steward of Gondor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentLoyalty Context triple: [Rangers of Ithilien, governmentLoyalty, Steward of Gondor]
-
A.
governmentSponsor
Indicates that a government entity provides funding, support, or backing for another entity, project, or activity.
-
B.
associatedWithGovernmentProgram
Indicates that an entity has a connection or involvement with a government-run program, initiative, or scheme.
-
C.
ledGovernment
Indicates that one entity served as the head or primary leader of the government of another entity.
-
D.
hasGovernmentServicesProvidedBy
Indicates that one entity receives its governmental services from, or is administratively served by, another entity.
-
E.
holderGovernment
Indicates that a government entity serves as the official holder, custodian, or controlling authority over another entity.
- F. None of above. chosen
Provenance (4 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
| PDg | Predicate description generation | batch_69fecb4be24481908bda6197d7fc32f4 |
completed | May 9, 2026, 5:51 a.m. |
Created at: April 28, 2026, 9:07 a.m.