Triple
T21217668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palanpur Agency |
E522877
|
entity |
| Predicate | usedTitleForHead |
P48145
|
FINISHED |
| Object | Political Agent |
—
|
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: Political Agent | Statement: [Palanpur Agency, usedTitleForHead, Political Agent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTitleForHead Context triple: [Palanpur Agency, usedTitleForHead, Political Agent]
-
A.
usedTitleIn
Indicates that one entity employed or referenced another entity as a title in some context.
-
B.
usedTitleFrom
Indicates that one entity has employed or adopted the title originating from another entity.
-
C.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
D.
usedAsTitleElement
Indicates that one entity functions as a title-forming component or element within another entity’s title.
-
E.
definesHeadTitle
chosen
Indicates that one entity specifies or assigns the official head title or primary designation for 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7347613308190a1c9f4ea51591d4b |
completed | April 21, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:42 p.m.