Triple
T8924027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strategic Commands of NATO |
E212495
|
entity |
| Predicate | coordinatesDomains |
P41143
|
FINISHED |
| Object | land |
—
|
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: land | Statement: [Strategic Commands of NATO, coordinatesDomains, land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinatesDomains Context triple: [Strategic Commands of NATO, coordinatesDomains, land]
-
A.
coordinateDomain
Indicates that two or more entities share the same coordinate system or spatial reference framework for describing positions.
-
B.
domainOfPosition
Indicates that something specifies or defines the domain (scope, area, or field) within which a particular position or role is applicable.
-
C.
coordinates
Indicates that one entity organizes, directs, or harmonizes the actions or efforts of another entity or group to achieve a unified outcome.
-
D.
indicatesDomain
chosen
Indicates a domain or area of knowledge, activity, or applicability to which something (such as a concept, resource, or entity) belongs or is relevant.
-
E.
coordinatesPositionsIn
Indicates that one entity organizes or aligns the positions or placement of other entities within a specified context or space.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6652d63881908821c8735984322a |
completed | April 1, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.