Triple
T29113418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleazar ben Shammua |
E736975
|
entity |
| Predicate | statusInSources |
P193188
|
FINISHED |
| Object | prominent sage of his generation |
—
|
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: prominent sage of his generation | Statement: [Eleazar ben Shammua, statusInSources, prominent sage of his generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInSources Context triple: [Eleazar ben Shammua, statusInSources, prominent sage of his generation]
-
A.
sourceStatus
Indicates the current state or condition of a given source within a process, system, or workflow.
-
B.
workStatusOfSource
Indicates the current employment or occupational status associated with the source entity.
-
C.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
D.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
E.
statusInDatabases
Indicates the current state or condition an entity has within one or more database systems.
- F. None of above. chosen
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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
| PDg | Predicate description generation | batch_69fd3a6905b88190ae12b43576f4cc63 |
completed | May 8, 2026, 1:20 a.m. |
Created at: April 28, 2026, 11:20 a.m.