Triple
T29377970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2015 Synod of Bishops on the Family |
E745055
|
entity |
| Predicate | documentUsed |
P3129
|
FINISHED |
| Object | Instrumentum laboris |
—
|
NE NERFINISHED |
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: Instrumentum laboris | Statement: [2015 Synod of Bishops on the Family, documentUsed, Instrumentum laboris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentUsed Context triple: [2015 Synod of Bishops on the Family, documentUsed, Instrumentum laboris]
-
A.
usedDocument
chosen
Indicates that one entity has employed, referenced, or otherwise made use of a particular document in performing an action or fulfilling a purpose.
-
B.
documentTypeUsed
Indicates that a particular type or category of document is employed or applied in a given context or activity.
-
C.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
D.
documentsNow
Indicates that an entity is currently documenting, recording, or writing about another entity at the present time.
-
E.
discussedDocument
Indicates that an entity has engaged in a discussion about a particular document.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 2:33 p.m.