Triple
T16608484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yasna |
E403504
|
entity |
| Predicate | commentedIn |
P5301
|
FINISHED |
| Object | Pahlavi Zoroastrian literature |
—
|
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: Pahlavi Zoroastrian literature | Statement: [Yasna, commentedIn, Pahlavi Zoroastrian literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commentedIn Context triple: [Yasna, commentedIn, Pahlavi Zoroastrian literature]
-
A.
commentedOnBy
Indicates that an entity has received a comment authored or posted by another entity.
-
B.
commentatedFor
Indicates that one entity provided live or recorded commentary or analysis for an event, performance, or broadcast on behalf of another entity (such as an organization, channel, or client).
-
C.
mentionedWith
Indicates that two entities are mentioned together or in close association within the same context, such as a document, sentence, or conversation.
-
D.
notedIn
chosen
Indicates that information about one entity is mentioned, recorded, or referenced within another entity, such as a document, record, or source.
-
E.
mentionedAs
Indicates that one entity is referred to or cited by name or description in the context 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e36093901881909b85af47f75879a9 |
completed | April 18, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.