Triple
T31416092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic Star |
E801396
|
entity |
| Predicate | cannotBeAwardedWith |
P174103
|
FINISHED |
| Object | Air Crew Europe Star without clasp |
—
|
NE NERFINISHED |
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: Air Crew Europe Star without clasp | Statement: [Atlantic Star, cannotBeAwardedWith, Air Crew Europe Star without clasp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotBeAwardedWith Context triple: [Atlantic Star, cannotBeAwardedWith, Air Crew Europe Star without clasp]
-
A.
cannotBeAwardedTo
Indicates that a particular entity is ineligible to receive a specified award, prize, or recognition.
-
B.
notAwardedWhen
Indicates that one entity is not granted, conferred, or given in the circumstances or conditions specified by another entity or event.
-
C.
canBeAwarded
Indicates that an entity is eligible to receive or be granted a particular award, prize, or honor.
-
D.
notAwardedFor
Indicates that a particular award, prize, or honor was explicitly not given in recognition of a specified work, achievement, or entity.
-
E.
canBeAwardedTo
Indicates that something is eligible to receive or be granted a particular award, honor, or recognition.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: April 30, 2026, 8:43 p.m.