Triple
T5486447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seal of the Supreme Court of India |
E123592
|
entity |
| Predicate | featuresTextLanguage |
P31857
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Seal of the Supreme Court of India, featuresTextLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTextLanguage Context triple: [Seal of the Supreme Court of India, featuresTextLanguage, English]
-
A.
featuresText
Indicates that an entity includes or presents a specific piece of text as one of its characteristics or contents.
-
B.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
C.
contentLanguage
chosen
Indicates the language in which the content is expressed or intended to be understood.
-
D.
languageOfProduct
Indicates the language in which a product is written, labeled, presented, or otherwise made available.
-
E.
linguisticFeature
Indicates a relationship where a linguistic property, pattern, or characteristic is attributed to or associated with a language-related entity (such as a word, phrase, or text).
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.