Triple
T36039666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO OF-9 |
E1042504
|
entity |
| Predicate | typicalEquivalence |
—
|
GENERATED |
| Object | full general |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEquivalence Context triple: [NATO OF-9, typicalEquivalence, full general]
-
A.
typeOfEquivalence
Indicates that two entities are considered equivalent under a specified notion or criterion of sameness.
-
B.
equivalentTo
Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given context.
-
C.
typicalBilateralEquivalent
chosen
Indicates that two entities are considered standard or typical counterparts to each other in a bilateral relationship or comparison.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
equivalentIn
Indicates that two entities are considered logically or functionally the same in meaning, status, or effect within a given context.
- F. None of above.
Provenance (1 batch)
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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.