Triple
T7658978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whisperers |
E173454
|
entity |
| Predicate | territoryPolicy |
P78615
|
FINISHED |
| Object | enforce strict borders |
—
|
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: enforce strict borders | Statement: [Whisperers, territoryPolicy, enforce strict borders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territoryPolicy Context triple: [Whisperers, territoryPolicy, enforce strict borders]
-
A.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
B.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
C.
territoryCorrespondedTo
Indicates that one territory matched, aligned with, or was equivalent to another territory in scope, boundaries, or designation.
-
D.
territorialStatus
Indicates the legal or political condition of control, sovereignty, or jurisdiction that applies to a specific territory.
-
E.
claimsTerritory
Indicates that one entity asserts ownership, control, or sovereign rights over a specific geographic area or region.
- 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_69c69955517c819085bc715b96d304d2 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7061cbc3c8190a917dd7e71214182 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015dd8fc8190bc5f52a12bd46209 |
completed | March 27, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69c7061b218c81909fff789ba4c10e58 |
completed | March 27, 2026, 10:35 p.m. |
Created at: March 27, 2026, 3:59 p.m.