Triple
T36930843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buz |
E913474
|
entity |
| Predicate | associatedWithTextualCorpus |
P95315
|
FINISHED |
| Object | Masoretic Text |
E387422
|
NE 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: Masoretic Text | Statement: [Buz, associatedWithTextualCorpus, Masoretic Text]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithTextualCorpus Context triple: [Buz, associatedWithTextualCorpus, Masoretic Text]
-
A.
corpus
Indicates that an entity is a collection or body of texts, documents, or linguistic data used as a unified set for analysis or reference.
-
B.
relatedToAuthorCorpus
Indicates a general association or connection between something and the body of works (corpus) produced by a particular author.
-
C.
hasPartOfCorpus
Indicates that one entity constitutes a component or segment of the overall corpus associated with another entity.
-
D.
associatedWithText
Indicates that an entity has a contextual or semantic connection to a specific piece of text.
-
E.
hasTextualCorpus
chosen
Indicates that an entity is associated with or possesses a collection of written or textual materials.
- F. None of above.
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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e1639a5988190b44b9e33c4dd2f00 |
completed | June 26, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.