Triple
T20180503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gwalior Residency |
E492712
|
entity |
| Predicate | hasRepresentativeRank |
P138992
|
FINISHED |
| Object | British political officer |
—
|
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: British political officer | Statement: [Gwalior Residency, hasRepresentativeRank, British political officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRepresentativeRank Context triple: [Gwalior Residency, hasRepresentativeRank, British political officer]
-
A.
representsRank
Indicates that one entity serves as the rank, status, or hierarchical level assigned to another entity.
-
B.
recognizedAsRepresentativeBy
Indicates that one entity is acknowledged or accepted by another entity as acting as its representative.
-
C.
hasEnlistedRank
Indicates that an individual holds an enlisted (non-officer) rank within a military or similar hierarchical organization.
-
D.
hasRealRank
Indicates that an entity is assigned a specific real-valued rank or position within an ordered scale or hierarchy.
-
E.
hasCoRepresentativeRole
Indicates that an entity shares or holds a co-representative role or position alongside another entity within the same representational context.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668eed2e88190b54b15e6545dbdf8 |
completed | April 20, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:36 p.m.