Triple
T3454742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieutenant (Australian Army) |
E72876
|
entity |
| Predicate | NATOequivalent |
P6062
|
FINISHED |
| Object | OF-1 |
—
|
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: OF-1 | Statement: [Lieutenant (Australian Army), NATOequivalent, OF-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NATOequivalent Context triple: [Lieutenant (Australian Army), NATOequivalent, OF-1]
-
A.
NATOcode
chosen
Indicates that there is a specified NATO (North Atlantic Treaty Organization) code assigned to or associated with an entity.
-
B.
isNATOAllyOf
Indicates that one entity is a member of NATO and has a formal alliance relationship with the other entity within the NATO framework.
-
C.
hasParticipatingNATOAllies
Indicates that an entity is involved in an activity, operation, or arrangement together with one or more NATO member states as allies.
-
D.
militaryEquivalence
Indicates that two or more entities possess comparable military capabilities, strength, or strategic power such that neither holds a clear military advantage over the other.
-
E.
positionOnNATO
Indicates a country's stance or alignment regarding membership in, support for, or opposition to NATO.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbaa5e2188190a8157cb8dcca8d30 |
completed | March 8, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69adae041d588190a84a02bca94adec8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.