Triple
T23227561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quattro pezzi sacri |
E581053
|
entity |
| Predicate | hasPartTextSource |
P150841
|
FINISHED |
| Object | Biblical text |
—
|
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: Biblical text | Statement: [Quattro pezzi sacri, hasPartTextSource, Biblical text]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartTextSource Context triple: [Quattro pezzi sacri, hasPartTextSource, Biblical text]
-
A.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
-
B.
hasTextFrom
chosen
Indicates that one entity contains, is derived from, or directly uses the textual content originating from another entity.
-
C.
hasFragmentSource
Indicates that something originates from, or is derived as a fragment of, a specified source entity.
-
D.
hasStringParts
Indicates that a whole string is composed of, or can be decomposed into, one or more constituent string segments or parts.
-
E.
hasPartOfCorpus
Indicates that one entity constitutes a component or segment of the overall corpus associated with another entity.
- 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f1922f5b4081908145d66ea7534493 |
completed | April 29, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:09 p.m.