Triple
T21186347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Commander of the Indian Empire |
E522088
|
entity |
| Predicate | awardStatusAfter1947 |
P143210
|
FINISHED |
| Object | no new appointments |
—
|
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: no new appointments | Statement: [Grand Commander of the Indian Empire, awardStatusAfter1947, no new appointments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardStatusAfter1947 Context triple: [Grand Commander of the Indian Empire, awardStatusAfter1947, no new appointments]
-
A.
namedAwardAfter
Indicates that an award has been given a name in honor of or derived from a particular person, group, or entity.
-
B.
namedAfterAwardYear
Indicates that one entity is named after the year in which a particular award was given or received.
-
C.
yearHonored
Indicates the specific year in which an entity received an honor, award, or formal recognition.
-
D.
awardEstablishedInHisHonorBy
Indicates that an award was created in honor of a specific person by a particular individual or organization.
-
E.
namedAfterAwardLaureateOf
Indicates that one entity is named after a person who is a laureate (recipient) of a particular award.
- 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73021671c8190a7b464ece7dbaadd |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:06 p.m.