Triple
T14863910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Lucian honours system |
E349568
|
entity |
| Predicate | basisOfAward |
P76535
|
FINISHED |
| Object | merit |
—
|
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: merit | Statement: [Saint Lucian honours system, basisOfAward, merit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basisOfAward Context triple: [Saint Lucian honours system, basisOfAward, merit]
-
A.
basedOnBidFor
Indicates that one action, decision, or entity is determined or derived from a specific bid submitted in a bidding process.
-
B.
qualificationAwardedBy
Indicates that a particular qualification was granted or conferred by a specific awarding body or institution.
-
C.
basisDefinition
Indicates that one entity serves as the foundational explanation, principle, or justification upon which another entity is defined or established.
-
D.
traditionallyAwardedTo
Indicates that something is customarily or historically given to a particular recipient or group as part of an established tradition.
-
E.
assignmentBasis
chosen
Indicates the criterion or rationale on which an assignment or allocation is determined.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded574d0ec8190a6afed672ba6c2f9 |
completed | April 15, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:54 a.m.