Triple
T5505505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bindusara |
E144428
|
entity |
| Predicate | realmExtent |
P8868
|
FINISHED |
| Object | most of the Indian subcontinent |
—
|
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: most of the Indian subcontinent | Statement: [Bindusara, realmExtent, most of the Indian subcontinent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realmExtent Context triple: [Bindusara, realmExtent, most of the Indian subcontinent]
-
A.
realmWithin
Indicates that one realm or domain is contained inside, or exists as a subset of, another realm or domain.
-
B.
realmType
Indicates the classification or category of a realm, specifying what kind or type of realm it is.
-
C.
territorialExtent
chosen
Indicates the geographic area or spatial range over which something extends, applies, or has jurisdiction.
-
D.
realm
Indicates that one entity is a domain, sphere of influence, or area of control associated with another entity.
-
E.
peakTerritorialExtent
Indicates the maximum geographic area or territorial size that an entity controlled or occupied at the height of its expansion.
- 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f0e91d08190a4db907030955bb3 |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:32 p.m.