Triple
T37117814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governor (India) |
E919163
|
entity |
| Predicate | notDescription |
P45839
|
FINISHED |
| Object | being directly under central control |
—
|
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: being directly under central control | Statement: [Governor (India), notDescription, being directly under central control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notDescription Context triple: [Governor (India), notDescription, being directly under central control]
-
A.
notDescribedAs
chosen
Indicates that an entity is explicitly not characterized, labeled, or referred to using a particular description or term.
-
B.
notAbout
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
-
C.
notUsedAt
Indicates that a particular entity is not utilized, applied, or active at a specified location, time, or context.
-
D.
notWellDocumented
Indicates that the subject lacks sufficient, clear, or comprehensive documentation.
-
E.
notUsedOver
Indicates that one entity has not been used, applied, or utilized for a duration exceeding a specified time period relative to another entity or reference point.
- 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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.