Triple
T35057245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yasna ceremony |
E1011500
|
entity |
| Predicate | requiresVestment |
P38265
|
FINISHED |
| Object | padan |
—
|
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: padan | Statement: [Yasna ceremony, requiresVestment, padan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresVestment Context triple: [Yasna ceremony, requiresVestment, padan]
-
A.
requiresInvestmentIncrease
Indicates that one entity’s continuation, success, or fulfillment is contingent on increasing the amount of investment provided by another entity.
-
B.
requiresVestments
chosen
Indicates that performing the related action or role necessitates wearing specific ceremonial or official vestments.
-
C.
requiresMinimumCapital
Indicates that one entity can only proceed, be valid, or be permitted if a specified minimum amount of capital is available or provided.
-
D.
coFinancingRequirement
Indicates that an action, project, or agreement requires additional financial contribution from one or more other parties beyond the primary source of funding.
-
E.
requiredPledgeFrom
Indicates that one entity mandates or demands a pledge or commitment from another entity as a prerequisite or condition.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff8ba3f8248190bbdf8e7ec2b35093 |
completed | May 9, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69ff8b41ba988190a7332e8317d10f09 |
completed | May 9, 2026, 7:30 p.m. |
Created at: May 3, 2026, 4:01 p.m.