Triple
T3467179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Seringapatam |
E73164
|
entity |
| Predicate | effectOnMysore |
P48967
|
FINISHED |
| Object | significant territorial loss |
—
|
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: significant territorial loss | Statement: [Treaty of Seringapatam, effectOnMysore, significant territorial loss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnMysore Context triple: [Treaty of Seringapatam, effectOnMysore, significant territorial loss]
-
A.
effectOnSystem
Indicates the influence, change, or impact that one entity, action, or condition has on the state or behavior of a system.
-
B.
effectOnSchedule
Indicates how an event, action, or condition changes, disrupts, or influences a planned schedule or timeline.
-
C.
hasTourismImpactOn
Indicates that one entity affects or influences the tourism levels, patterns, or attractiveness of another entity.
-
D.
placeOfEffect
Indicates the location or setting where an action, event, or effect takes place or is realized.
-
E.
effectOfSong
Indicates the influence or impact that a particular song has on something, such as a listener, mood, or situation.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb1090188190ac8aafd87dfaa6a7 |
completed | March 8, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:17 p.m.