Triple
T21556598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas the Israelite |
E531907
|
entity |
| Predicate | textualStatusOfWork |
P68792
|
FINISHED |
| Object | apocryphal gospel |
—
|
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: apocryphal gospel | Statement: [Thomas the Israelite, textualStatusOfWork, apocryphal gospel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textualStatusOfWork Context triple: [Thomas the Israelite, textualStatusOfWork, apocryphal gospel]
-
A.
traditionalWritingStatus
Indicates the status or condition of something with respect to its use of traditional writing forms or scripts.
-
B.
legalFormOfWork
Indicates the legally defined type or classification of employment or work arrangement under which an activity is performed.
-
C.
writingsStatus
Indicates the status or condition of a set of writings (e.g., whether they are drafted, reviewed, published, or otherwise processed) in relation to an entity.
-
D.
statusInText
Indicates that the text explicitly states or conveys the status or condition of an entity.
-
E.
textStatus
chosen
Indicates the current state or condition of a piece of text, such as its progress, validity, or processing outcome.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2e04b048190ac3a9913094b4625 |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:29 p.m.