Triple
T34525552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patriarchate of the East Indies |
E886388
|
entity |
| Predicate | hasNoProperTerritory |
P204121
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Patriarchate of the East Indies, hasNoProperTerritory, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoProperTerritory Context triple: [Patriarchate of the East Indies, hasNoProperTerritory, true]
-
A.
hasDefinedTerritory
Indicates that an entity possesses a specific, delimited geographic or conceptual area over which it has recognized control or jurisdiction.
-
B.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
C.
hasNonContiguousTerritory
Indicates that an entity’s territory consists of two or more separate, non-adjacent areas rather than one continuous region.
-
D.
usesTerritoryFor
Indicates that an entity employs or exploits a particular territory for a specific purpose, function, or activity.
-
E.
isForTerritory
Indicates that something is intended to define, cover, or apply to a specific territory or geographic area.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0326d40cb88190802f61fa832f8ca8 |
completed | May 12, 2026, 1:10 p.m. |
| PD | Predicate disambiguation | batch_6a03268b4f9c8190b3e135b37ed373c3 |
completed | May 12, 2026, 1:09 p.m. |
| PDg | Predicate description generation | batch_6a0326d30068819096da11fba14c2f31 |
completed | May 12, 2026, 1:10 p.m. |
Created at: May 1, 2026, 2:02 a.m.