Triple
T38498923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murud-Janjira Fort |
E919773
|
entity |
| Predicate | neverConqueredBy |
P137315
|
FINISHED |
| Object | Marathas |
—
|
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: Marathas | Statement: [Murud-Janjira Fort, neverConqueredBy, Marathas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neverConqueredBy Context triple: [Murud-Janjira Fort, neverConqueredBy, Marathas]
-
A.
notConqueredBy
chosen
Indicates that one entity has not been taken over, subdued, or brought under the control of another entity.
-
B.
neverFullyColonizedBy
Indicates that no external power ever achieved complete political, economic, or administrative control over the referenced entity.
-
C.
neverEffectivelyRuled
Indicates that the subject was formally in a position of authority over the object but at no point exercised real or effective control or governance.
-
D.
realmConqueredBy
Indicates that a particular realm or territory has been taken over and brought under the control of a specified conqueror.
-
E.
conqueredInPartBy
Indicates that one entity has gained control over a portion, but not the entirety, of another entity through conquest.
- 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.