Triple
T10297922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junkers G 38 |
E241544
|
entity |
| Predicate | NATOname |
P92974
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Junkers G 38, NATOname, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NATOname Context triple: [Junkers G 38, NATOname, none]
-
A.
NATOcode
Indicates that there is a specified NATO (North Atlantic Treaty Organization) code assigned to or associated with an entity.
-
B.
NATOCategory
Indicates that an entity is classified according to a specific NATO-defined category or designation.
-
C.
isNATOAllyOf
Indicates that one entity is a member of NATO and has a formal alliance relationship with the other entity within the NATO framework.
-
D.
NATOAccessionYear
Indicates the year in which an entity formally became a member of NATO.
-
E.
alliedCountries
Indicates that two countries are formally cooperating as allies, typically through mutual support agreements or shared strategic interests.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2ed50908190962f0d6d049fb964 |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d29d7cf08190acd70cee634c5cdb |
completed | April 7, 2026, 9:47 a.m. |
Created at: April 6, 2026, 11:43 a.m.