Triple
T18265726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Navy Chaplaincy |
E437477
|
entity |
| Predicate | chaplainsAre |
P131097
|
FINISHED |
| Object | commissioned officers |
—
|
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: commissioned officers | Statement: [Royal Navy Chaplaincy, chaplainsAre, commissioned officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chaplainsAre Context triple: [Royal Navy Chaplaincy, chaplainsAre, commissioned officers]
-
A.
hasChaplain
Indicates that an entity is served or attended to by a designated chaplain.
-
B.
clergyCan
Indicates that members of the clergy are permitted or authorized to perform a specified action or exercise a particular role or function.
-
C.
clergy
Indicates that an entity serves in an official religious or spiritual leadership role within an organized faith or religious institution.
-
D.
clergySystem
Indicates a relationship in which an organized religious institution or tradition has a structured system of clergy roles, ranks, or offices.
-
E.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff79851481909a4bbeb14fb00647 |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:34 a.m.