Triple
T5739514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Armed Police Forces (Assistant Commandants) Examination |
E126578
|
entity |
| Predicate | writtenPapers |
P65565
|
FINISHED |
| Object | Paper I |
—
|
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: Paper I | Statement: [Central Armed Police Forces (Assistant Commandants) Examination, writtenPapers, Paper I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenPapers Context triple: [Central Armed Police Forces (Assistant Commandants) Examination, writtenPapers, Paper I]
-
A.
paperArchive
Indicates that a paper is stored, preserved, or made available within a particular archive or archival system.
-
B.
publishedDocument
Indicates that an entity has formally issued or made a document publicly available.
-
C.
areWrittenOn
Indicates that one entity serves as a surface or medium on which another entity is inscribed, recorded, or written.
-
D.
written
Indicates that one entity has created or authored a text, document, or written work involving or about another entity.
-
E.
wrote
Indicates that an entity is the author or creator of a written work involving another entity.
- 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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0255dc35c8190ab9ee5d269ce553a |
completed | March 22, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c022a50c048190aff24c63e7039dd6 |
completed | March 22, 2026, 5:11 p.m. |
Created at: March 22, 2026, 3:48 p.m.