Triple
T2860354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hellenic Air Force |
E63303
|
entity |
| Predicate | usesFinFlash |
P43707
|
FINISHED |
| Object | Greek national colors |
—
|
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: Greek national colors | Statement: [Hellenic Air Force, usesFinFlash, Greek national colors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFinFlash Context triple: [Hellenic Air Force, usesFinFlash, Greek national colors]
-
A.
isSupportedBy
Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
-
B.
usedSupport
Indicates that one entity employed or relied on another entity as a means of support or assistance in performing an action or achieving a result.
-
C.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
D.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
E.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf8c676c8190ab29f89d50bd09c3 |
completed | March 7, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69abdd10aef88190b750aae07e7df4dc |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdee94c2081908e5075e87e70780a |
completed | March 7, 2026, 8:16 a.m. |
Created at: March 6, 2026, 10:02 p.m.