Triple
T36992944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | گریگورین کیلنڈر |
E915152
|
entity |
| Predicate | متعلقہ_معیار |
P113456
|
FINISHED |
| Object | آئی ایس او 8601 تاریخ اور وقت کا معیار |
—
|
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: آئی ایس او 8601 تاریخ اور وقت کا معیار | Statement: [گریگورین کیلنڈر, متعلقہ_معیار, آئی ایس او 8601 تاریخ اور وقت کا معیار]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: متعلقہ_معیار Context triple: [گریگورین کیلنڈر, متعلقہ_معیار, آئی ایس او 8601 تاریخ اور وقت کا معیار]
-
A.
relatedMeasure
chosen
Indicates that one measure is associated with or connected to another measure in a relevant way.
-
B.
relatedMetric
Indicates that one metric has a defined relationship or dependency with another metric.
-
C.
measurementRelatedTo
Indicates that there is a meaningful association or linkage between two or more measurements, such as dependency, comparison, or contextual relevance.
-
D.
conditionRelatesTo
Indicates that one condition is relevant, connected, or applicable to another condition or contextual factor.
-
E.
関連原則
Indicates a principle that is associated with, governs, or is otherwise relevant to another concept, rule, or situation.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.