Triple
T2526531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amrit Sanchar |
E56045
|
entity |
| Predicate | agePolicy |
P39362
|
FINISHED |
| Object | open to any age capable of understanding vows |
—
|
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: open to any age capable of understanding vows | Statement: [Amrit Sanchar, agePolicy, open to any age capable of understanding vows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agePolicy Context triple: [Amrit Sanchar, agePolicy, open to any age capable of understanding vows]
-
A.
expirationPolicy
Indicates the rules or conditions under which something becomes invalid, unusable, or no longer in effect after a certain time or event.
-
B.
preservationPolicy
Indicates the rules or strategy governing how something is maintained, protected, and retained over time.
-
C.
locationPolicy
Indicates a rule or constraint governing where an entity is allowed, required, or restricted to be located.
-
D.
ageProgression
Indicates a temporal relationship where an entity’s age increases or advances over time.
-
E.
agePattern
Indicates a relationship where entities share or follow a specific configuration, distribution, or rule regarding their ages.
- 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd255f0d081908d20cfb812c4bfc1 |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c2e34c8190a914d5c2afba147c |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd18e72a88190bdcf12b326d42fad |
completed | March 7, 2026, 7:19 a.m. |
Created at: March 6, 2026, 9:46 p.m.