Triple
T1005075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Cross |
E21689
|
entity |
| Predicate | canBeAwardedCollectively |
P21725
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [George Cross, canBeAwardedCollectively, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeAwardedCollectively Context triple: [George Cross, canBeAwardedCollectively, true]
-
A.
canBeAwardedTo
Indicates that something is eligible to receive or be granted a particular award, honor, or recognition.
-
B.
canBeAwardedMultipleTimes
Indicates that the associated award, honor, or recognition may be granted to the same recipient on more than one occasion.
-
C.
canAward
Indicates that one entity has the authority or ability to grant an award, honor, or recognition to another entity.
-
D.
isIndividualOrTeamAward
Indicates that an award is given either to a single individual or collectively to a team, rather than to another type of recipient.
-
E.
hasCollectiveRightClaim
Indicates that a group or collective entity asserts or holds a right or entitlement on behalf of its members.
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b51303548190a5ee3c0797fc3245 |
completed | March 1, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b2e7108190b338b6c19d4aff55 |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b326d9d88190913c1a892a795707 |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:41 p.m.