Triple
T23752377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gospel of Luke 23:38 |
E587003
|
entity |
| Predicate | inscriptionAuthority |
P18434
|
FINISHED |
| Object | Roman governance |
—
|
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: Roman governance | Statement: [Gospel of Luke 23:38, inscriptionAuthority, Roman governance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionAuthority Context triple: [Gospel of Luke 23:38, inscriptionAuthority, Roman governance]
-
A.
recordAuthority
Indicates that an entity serves as the authoritative source or controlling body responsible for creating, maintaining, or validating a particular record.
-
B.
inscriptionBy
chosen
Indicates that an inscription was created, written, or carved by a particular agent or entity.
-
C.
signatoryAuthority
Indicates that an entity has the legal power or authorization to sign documents or agreements on behalf of another party.
-
D.
designationAuthority
Indicates the entity that has the official power or responsibility to assign, grant, or confer a particular designation to another entity.
-
E.
inscriptionStatus
Indicates the current state or condition of an inscription, such as whether it has been created, verified, updated, or removed.
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcc3a06c81908e8a6e1f531c73bc |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:13 p.m.