Triple
T8719914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French regions |
E206984
|
entity |
| Predicate | havePowerOver |
P544
|
FINISHED |
| Object | regional transport |
—
|
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: regional transport | Statement: [French regions, havePowerOver, regional transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: havePowerOver Context triple: [French regions, havePowerOver, regional transport]
-
A.
hasPower
chosen
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
B.
hasNoPowerOver
Indicates that one entity lacks authority, control, or influence over another entity or situation.
-
C.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
D.
typeOfPowerGranted
Indicates the specific kind or category of power or authority that is conferred from one entity to another.
-
E.
hasNumberOfPowers
Indicates the quantity of distinct powers or abilities that an entity possesses.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d02a52c81909f93622ae6920b80 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.