Triple
T31498875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tipra |
E803620
|
entity |
| Predicate | autonomousCouncil |
P116034
|
FINISHED |
| Object | TTAADC |
—
|
NE NERFINISHED |
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: TTAADC | Statement: [Tipra, autonomousCouncil, TTAADC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autonomousCouncil Context triple: [Tipra, autonomousCouncil, TTAADC]
-
A.
governmentDistrict
Indicates that a government entity has jurisdiction over or is administratively associated with a specific district.
-
B.
hasRegionalBoard
Indicates that an entity is overseen, governed, or managed by a specific regional board.
-
C.
isCouncilAreaOf
Indicates that one entity is the officially designated council (local government) area that administers or governs the other entity.
-
D.
zonalCouncil
chosen
Indicates a relationship where an entity is part of, governed by, or associated with a specific zonal council within a larger administrative or organizational structure.
-
E.
administrativeCouncilArea
Indicates that one entity is an administrative council area within which the other entity is located or governed.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a1ebc9d8819082794ae663fff63d |
completed | May 3, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:43 p.m.