Triple
T23752344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gospel of Luke 23:38 |
E587003
|
entity |
| Predicate | recordsObject |
P153554
|
FINISHED |
| Object | inscription above Jesus on the cross |
—
|
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: inscription above Jesus on the cross | Statement: [Gospel of Luke 23:38, recordsObject, inscription above Jesus on the cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsObject Context triple: [Gospel of Luke 23:38, recordsObject, inscription above Jesus on the cross]
-
A.
recordsWith
Indicates that one entity keeps or maintains documented information about another entity or event.
-
B.
recordsType
Indicates that one entity documents, stores, or keeps an official account of a particular type or category of information, event, or item.
-
C.
recordStructure
Indicates a relationship where an entity defines, organizes, or specifies the internal layout and components of a record or data structure.
-
D.
recordDetail
Indicates that one entity stores or documents specific information or attributes about another entity.
-
E.
recordsQuestion
Indicates that an entity captures or logs a question, preserving it as a record.
- 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_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. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:13 p.m.