Triple
T21287549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 129 of the Constitution of India |
E524700
|
entity |
| Predicate | designatesAs |
P49802
|
FINISHED |
| Object | court of record |
—
|
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: court of record | Statement: [Article 129 of the Constitution of India, designatesAs, court of record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatesAs Context triple: [Article 129 of the Constitution of India, designatesAs, court of record]
-
A.
designationFor
chosen
Indicates that one entity serves as the official title, label, or role name assigned to another entity.
-
B.
knowsAs
Indicates that one entity recognizes or refers to another entity by a particular name, alias, or identifier.
-
C.
designatesAuthority
Indicates that one entity formally assigns or confers decision-making power or control over something to another entity.
-
D.
canBeDesignatedBy
Indicates that one entity is capable of being assigned, labeled, or identified by another entity as its designation.
-
E.
designationBasedOn
Indicates that one entity’s designation, label, or title is assigned or determined on the basis of another entity or criterion.
- 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_69e0b5171f6c8190a5d57201ede73811 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736d7c57c8190bc4180ea590a62d4 |
completed | April 21, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:03 p.m.