Triple
T6909213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Laity |
E159887
|
entity |
| Predicate | locatedInDocumentAfter |
P4527
|
FINISHED |
| Object | chapter on the People of God |
—
|
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: chapter on the People of God | Statement: [The Laity, locatedInDocumentAfter, chapter on the People of God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDocumentAfter Context triple: [The Laity, locatedInDocumentAfter, chapter on the People of God]
-
A.
locatedAfter
chosen
Indicates that one entity is positioned later than another along a defined sequence, order, or spatial/temporal axis.
-
B.
locationInDocument
Indicates that one entity specifies where another entity is situated or referenced within a document.
-
C.
subsequentDocument
Indicates that one document follows another in sequence, typically as a later or next installment, version, or related record.
-
D.
declaredInDocument
Indicates that something (such as an entity, concept, or statement) is formally specified or announced within a particular document.
-
E.
namedAfterPosition
Indicates that an entity is named after a specific position, role, or rank associated with it.
- 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9be98748190b5cb698e66e3aa42 |
completed | March 27, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:25 p.m.