Triple
T34437231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silas |
E883995
|
entity |
| Predicate | carriedDocument |
P171352
|
FINISHED |
| Object | Jerusalem Council letter |
—
|
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: Jerusalem Council letter | Statement: [Silas, carriedDocument, Jerusalem Council letter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedDocument Context triple: [Silas, carriedDocument, Jerusalem Council letter]
-
A.
bringsDocument
chosen
Indicates that one entity delivers or carries a document to another entity or location.
-
B.
holdsDocumentsFrom
Indicates that an entity possesses or retains documents that originate from or are issued by another specified entity.
-
C.
confirmationDocument
Indicates that there exists a document serving as formal confirmation or verification of an action, event, or agreement between entities.
-
D.
issuedDocument
Indicates that one entity has formally created and provided an official document to another entity.
-
E.
documentProclaimed
Indicates that a document formally announces, declares, or makes an official proclamation about something.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2 a.m.