Triple
T17449402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quezon Service Cross (posthumous) |
E424872
|
entity |
| Predicate | awardCondition |
P216
|
FINISHED |
| Object | awarded after death |
—
|
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: awarded after death | Statement: [Quezon Service Cross (posthumous), awardCondition, awarded after death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardCondition Context triple: [Quezon Service Cross (posthumous), awardCondition, awarded after death]
-
A.
awardCriteria
chosen
Indicates the standards or conditions used to determine eligibility for receiving an award or recognition.
-
B.
awardCurrency
Indicates that one entity grants or gives a specified amount of currency to another entity.
-
C.
awardEffect
Indicates that one entity confers or grants a benefit, recognition, or reward that has a particular impact or consequence on another entity.
-
D.
awardStatus
Indicates the current state or outcome of an award in relation to an entity, such as whether it has been granted, pending, rejected, or completed.
-
E.
canAward
Indicates that one entity has the authority or ability to grant an award, honor, or recognition to another entity.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4513b99908190a6b5833559856c8b |
completed | April 19, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.