Triple
T32853988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palghat |
E840326
|
entity |
| Predicate | fortControlledBy |
P97456
|
FINISHED |
| Object | Kingdom of Mysore |
—
|
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: Kingdom of Mysore | Statement: [Palghat, fortControlledBy, Kingdom of Mysore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortControlledBy Context triple: [Palghat, fortControlledBy, Kingdom of Mysore]
-
A.
isUnderControlOf
chosen
Indicates that one entity is subject to the authority, direction, or governance of another entity.
-
B.
isControlledUnder
Indicates that one entity is subject to regulatory, legal, or authoritative control exercised by another entity or governing framework.
-
C.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
-
D.
effectControlledBy
Indicates that the occurrence, magnitude, or outcome of one effect is regulated, determined, or constrained by another specified factor or agent.
-
E.
exertsControlOver
Indicates that one entity has the power or authority to direct, influence, or determine the actions or decisions of 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce7ba5b88190a2bc14d4f7d63013 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:17 a.m.