Triple
T15521856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euro-Atlantic area |
E368987
|
entity |
| Predicate | hasKeyDimension |
P118977
|
FINISHED |
| Object | political cooperation |
—
|
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: political cooperation | Statement: [Euro-Atlantic area, hasKeyDimension, political cooperation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyDimension Context triple: [Euro-Atlantic area, hasKeyDimension, political cooperation]
-
A.
hasDimension
Indicates that an entity possesses a specific measurable extent or size along one or more axes (e.g., length, width, height).
-
B.
hasKeyMeasure
Indicates that one entity is the primary or defining metric, indicator, or quantitative measure used to assess or evaluate another entity.
-
C.
hasDimensionality
Indicates that an entity possesses a specific number of dimensions or a particular dimensional structure.
-
D.
hasDimensionID
Indicates that an entity is associated with a specific dimension through its unique identifier.
-
E.
hasDimensionParameter
Indicates that an entity is associated with a specific dimensional parameter (such as size, length, width, or height) that characterizes its measurable extent.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0403543188190abac49d2b9decb89 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57165288190979b7acb71ad5145 |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 4:04 a.m.