Triple
T149751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | field marshal |
E3405
|
entity |
| Predicate | NATOcode |
P6062
|
FINISHED |
| Object | OF-10 |
—
|
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-10 | Statement: [field marshal, NATOcode, OF-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NATOcode Context triple: [field marshal, NATOcode, OF-10]
-
A.
isNATOAllyOf
Indicates that one entity is a member of NATO and has a formal alliance relationship with the other entity within the NATO framework.
-
B.
UNMemberState
Indicates that a country is a recognized member state of the United Nations.
-
C.
countryJoined
Indicates that a country became a member of, or formally entered into, a specific organization, union, alliance, or agreement.
-
D.
NUTSRegionCode
Indicates the classification of an entity according to the NUTS (Nomenclature of Territorial Units for Statistics) regional coding system used for statistical regions.
-
E.
ISOCode
Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a256599db08190a7b000b381d32ec4 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a25737f9188190b9690dce98aed83a |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.