Triple
T3770595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Secretary |
E82786
|
entity |
| Predicate | canExistAt |
P51053
|
FINISHED |
| Object | subnational level in some countries |
—
|
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: subnational level in some countries | Statement: [State Secretary, canExistAt, subnational level in some countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canExistAt Context triple: [State Secretary, canExistAt, subnational level in some countries]
-
A.
existsFor
Indicates that something is present, available, or holds true for a particular entity, context, or condition.
-
B.
existedUnder
Indicates that one entity existed within the authority, jurisdiction, or domain of another entity during a certain period.
-
C.
isAt
Indicates that one entity is located at or present in the place or position of another entity.
-
D.
existedAs
Indicates that one entity had the status, form, or identity of another entity during a certain time or context.
-
E.
areAccessibleAt
Indicates that certain entities can be reached, used, or entered at a specified location, time, or context.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc307cf8819090730b5e697bb197 |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc133ef50819094c2b971f31f1615 |
completed | March 8, 2026, 6:34 p.m. |
Created at: March 8, 2026, 3:36 p.m.