Triple
T547746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon Commission |
E12768
|
entity |
| Predicate | appointedOn |
P15564
|
FINISHED |
| Object | 1927-11-08 |
—
|
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: 1927-11-08 | Statement: [Simon Commission, appointedOn, 1927-11-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedOn Context triple: [Simon Commission, appointedOn, 1927-11-08]
-
A.
appointedFor
Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
-
B.
convenedOn
Indicates that an event, meeting, or formal gathering took place or was held on a specific date or time.
-
C.
ordinationDate
Indicates the date on which an individual was formally ordained to a religious office or role.
-
D.
appointmentOnAdviceOf
Indicates that an appointment or selection of someone to a position is made based on the recommendation, counsel, or formal advice of another person or authority.
-
E.
decisionDate
Indicates the date on which a specific decision was formally made or finalized.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a498e2e8c88190a66d759ed3094e18 |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494b957988190bc269e372df2f0b2 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49858abd48190bd4b002a93e4a908 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.