Triple
T23932111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yah |
E602526
|
entity |
| Predicate | exampleOfUseInNames |
P41975
|
FINISHED |
| Object | Isaiah (Yeshayahu) |
—
|
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: Isaiah (Yeshayahu) | Statement: [Yah, exampleOfUseInNames, Isaiah (Yeshayahu)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleOfUseInNames Context triple: [Yah, exampleOfUseInNames, Isaiah (Yeshayahu)]
-
A.
nameUsedIn
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
B.
usedAsExampleIn
chosen
Indicates that one entity is cited or presented as an illustrative example within another entity, such as a text, discussion, or explanation.
-
C.
oftenUsedAsNameFor
Indicates that something frequently serves as a name or designation for another entity.
-
D.
usedInNamingPractice
Indicates that something serves as a basis, source, or reference in the practice of assigning names.
-
E.
usedInFullNameOf
Indicates that one entity (such as a word, name part, or title) is used as a component within the complete formal name of 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1cf9c223881908e5fa4b5564848e6 |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:58 p.m.