Triple
T36039666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO OF-9 |
E1042504
|
entity |
| Predicate | typicalEquivalence |
P119967
|
FINISHED |
| Object | full general |
—
|
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: full general | Statement: [NATO OF-9, typicalEquivalence, full general]
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 (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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.