Triple
T31645358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adi tala |
E807569
|
entity |
| Predicate | supportsSubdivisions |
P207480
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Adi tala, supportsSubdivisions, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSubdivisions Context triple: [Adi tala, supportsSubdivisions, 3]
-
A.
hasSubdivision
Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
-
B.
hasSubdivisionStandard
Indicates that a governing standard or specification defines how an entity is to be subdivided into smaller parts or units.
-
C.
hasHigherLevelSubdivision
Indicates that one administrative or organizational unit is contained within and subordinate to a larger, higher-level subdivision.
-
D.
hasNationalSubdivisionType
Indicates that an entity is associated with a specific type or category of national-level administrative subdivision (e.g., state, province, region).
-
E.
hasSubdivisionCode
Indicates that an entity is associated with a specific code identifying one of its internal subdivisions (such as a state, province, or region).
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 30, 2026, 10:50 p.m.