Triple
T26406358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vrtača |
E663843
|
entity |
| Predicate | isInNationalTerritoryOf |
P45703
|
FINISHED |
| Object | Carinthia, Austria |
—
|
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: Carinthia, Austria | Statement: [Vrtača, isInNationalTerritoryOf, Carinthia, Austria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInNationalTerritoryOf Context triple: [Vrtača, isInNationalTerritoryOf, Carinthia, Austria]
-
A.
isInGeopoliticalEntity
chosen
Indicates that one entity is located within, or is a part of, a specific geopolitical unit such as a country, state, or city.
-
B.
locatedOnTerritoryOf
Indicates that one entity is situated within or on the land area governed or owned by another entity.
-
C.
hasTerritorialInterestIn
Indicates that an entity claims, seeks, or maintains control, influence, or rights over a specific geographic area or territory.
-
D.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
E.
refersToNationWithin
Indicates that one entity makes reference to, or is about, a specific nation that exists within a larger geopolitical or contextual scope.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610f87374819084279ca5c2f3d32f |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 11:35 p.m.