Triple
T4406211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Response Force |
E93737
|
entity |
| Predicate | isRotational |
P56077
|
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: [NATO Response Force, isRotational, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRotational Context triple: [NATO Response Force, isRotational, true]
-
A.
rotationType
Indicates the specific kind or mode of rotational movement or orientation applied in a given context.
-
B.
rotatesWith
Indicates that two or more entities turn or spin together in a coordinated or mechanically linked manner, typically sharing the same rotational motion or axis.
-
C.
isRapidlyRotating
Indicates that an entity is spinning or rotating at a very high angular speed relative to a typical or reference rate.
-
D.
hasChaoticRotation
Indicates that an object rotates in a highly irregular, unpredictable manner rather than following a stable, consistent spin.
-
E.
rotatesAmong
Indicates that an entity takes turns occupying or performing a role, position, or function in sequence with other entities.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b35489f6948190a4b2c259f64b4abf |
completed | March 13, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3509997208190933f167f7e20ccfa |
completed | March 12, 2026, 11:47 p.m. |
Created at: March 12, 2026, 11:28 p.m.