Triple
T6797359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DY |
E156089
|
entity |
| Predicate | operatorAllianceStatus |
P14509
|
FINISHED |
| Object | non-allied |
—
|
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: non-allied | Statement: [DY, operatorAllianceStatus, non-allied]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorAllianceStatus Context triple: [DY, operatorAllianceStatus, non-allied]
-
A.
allianceStatus
chosen
Indicates the formal or informal cooperative relationship between entities, such as whether they are allies, neutral, or adversarial.
-
B.
hasAllianceInState
Indicates that an alliance or cooperative relationship exists between entities within a specified state or jurisdiction.
-
C.
allianceType
Indicates the specific kind or category of alliance relationship that exists between entities.
-
D.
allianceCompatibility
Indicates that two or more entities are suitable or well-matched to form or maintain an alliance based on their respective attributes, goals, or constraints.
-
E.
allianceRole
Indicates the specific function, status, or responsibility an entity holds within an alliance or cooperative partnership.
- 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_69c6881844448190a65822d9b39d7f88 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2ca0c288190a990180fb7cfd08f |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:15 p.m.