Triple
T8631840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owl |
E204420
|
entity |
| Predicate | refersToDesignationSystem |
P75661
|
FINISHED |
| Object | Allied code name system for Axis aircraft |
—
|
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: Allied code name system for Axis aircraft | Statement: [Owl, refersToDesignationSystem, Allied code name system for Axis aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToDesignationSystem Context triple: [Owl, refersToDesignationSystem, Allied code name system for Axis aircraft]
-
A.
systemDesignation
Indicates that an entity has been assigned a specific formal label or identifier within a defined system or framework.
-
B.
hasInternalDesignationFor
chosen
Indicates that one entity assigns or uses an internal label, code, or designation to refer to another entity.
-
C.
hasDesignationBy
Indicates that one entity has been formally assigned or labeled with a specific designation by another entity.
-
D.
designationFor
Indicates that one entity serves as the official title, label, or role name assigned to another entity.
-
E.
hasDesignation
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc455906f8819082edd79cb4a1cf28 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.