Triple
T14023904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Complutensian Polyglot Bible |
E337405
|
entity |
| Predicate | workOnProjectBegan |
P36447
|
FINISHED |
| Object | 1502 |
—
|
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: 1502 | Statement: [Complutensian Polyglot Bible, workOnProjectBegan, 1502]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workOnProjectBegan Context triple: [Complutensian Polyglot Bible, workOnProjectBegan, 1502]
-
A.
collaborationStartWork
chosen
Indicates the point in time when a collaborative effort between entities begins or is initiated.
-
B.
workOn
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
-
C.
workOnItEnded
Indicates that an entity’s involvement in working on a particular task, project, or item has come to an end.
-
D.
useBegan
Indicates that an entity initiated or started using another entity or resource at a particular point in time.
-
E.
isOnProject
Indicates that an entity is currently assigned to, involved with, or working on a particular project.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3d87b88190b038d334f4965369 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.