Triple
T19025212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cantonments Act, 2006 |
E465590
|
entity |
| Predicate | languageOfAuthoritativeText |
P27218
|
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: [Cantonments Act, 2006, languageOfAuthoritativeText, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfAuthoritativeText Context triple: [Cantonments Act, 2006, languageOfAuthoritativeText, English]
-
A.
languageOfWritings
Indicates that a specified language is the one in which certain writings or written works are composed.
-
B.
isLanguageOf
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
-
C.
languageOfSources
Indicates that the specified language is the language in which the referenced sources or source materials are expressed.
-
D.
languageOfPromulgation
chosen
Indicates the language in which a law, decree, or official act is formally issued or proclaimed.
-
E.
originalTextLanguage
Indicates the language in which a text was originally written or created before any translation or adaptation.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6e271848190b67ad08af35b6796 |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.