Triple
T36812699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bharata (India) |
E909637
|
entity |
| Predicate | modernScope |
P194831
|
FINISHED |
| Object | territory of the Republic of India |
—
|
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: territory of the Republic of India | Statement: [Bharata (India), modernScope, territory of the Republic of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernScope Context triple: [Bharata (India), modernScope, territory of the Republic of India]
-
A.
modernAccess
Indicates that an entity has contemporary, up-to-date means or methods of accessing or interacting with another entity or resource.
-
B.
modernUse
Indicates how something is currently used or applied in modern times.
-
C.
modernVariation
Indicates that one entity is a contemporary or updated version, adaptation, or reinterpretation of another.
-
D.
modernDimension
Indicates a relationship where something is characterized by or associated with contemporary or current-era qualities, styles, or conditions.
-
E.
modernSymbol
Indicates that something functions as a contemporary or current-era symbol representing or standing for something else.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
| PDg | Predicate description generation | batch_69fd884b9d908190833de9500ff6d62a |
completed | May 8, 2026, 6:52 a.m. |
Created at: May 3, 2026, 4:13 p.m.