Triple
T3007442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yahya |
E81936
|
entity |
| Predicate | reveredFor |
P30748
|
FINISHED |
| Object | piety |
—
|
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: piety | Statement: [Yahya, reveredFor, piety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reveredFor Context triple: [Yahya, reveredFor, piety]
-
A.
veneratedFor
chosen
Indicates that one entity is highly respected, honored, or revered because of a particular quality, achievement, or characteristic of another entity.
-
B.
respectedAs
Indicates that one entity regards another with esteem or honor, recognizing their value, status, or authority.
-
C.
historicallyPrizedFor
Indicates that something has been especially valued or esteemed for a particular quality, use, or significance in the past.
-
D.
veneratedBy
Indicates that one entity is regarded with deep respect, reverence, or worship by another entity.
-
E.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- 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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a4a12508190a48ae1c86233d25e |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad96180eb08190a524c5f458d41382 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.