Triple
T23033619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldansky District |
E573533
|
entity |
| Predicate | hasLargeTerritory |
P150730
|
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: [Aldansky District, hasLargeTerritory, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLargeTerritory Context triple: [Aldansky District, hasLargeTerritory, true]
-
A.
hasMajorTerritory
Indicates that one entity possesses or controls the primary geographic area or domain associated with another entity.
-
B.
isLargestTerritoryOf
Indicates that one territory is the largest, by area or extent, among all territories belonging to a specified entity.
-
C.
hasOverseasTerritory
Indicates that one entity possesses or controls a territory located outside its own primary geographic or sovereign domain.
-
D.
hasLargestContinuousLandAreaOn
Indicates that an entity possesses the greatest uninterrupted expanse of land on a specified geographic region or surface compared to all other entities.
-
E.
expandedTerritoryOf
Indicates that one entity has increased or extended the geographic or jurisdictional area belonging to another entity.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18482e78c8190a89681eec2edb812 |
completed | April 29, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:53 p.m.