Triple
T951853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aosta Valley |
E20538
|
entity |
| Predicate | isAutonomous |
P5082
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Aosta Valley, isAutonomous, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAutonomous Context triple: [Aosta Valley, isAutonomous, true]
-
A.
hasAutonomyWithin
Indicates that one entity possesses independent decision-making power or self-governance within the scope, domain, or boundaries defined by another entity.
-
B.
isDriverless
Indicates that something operates or moves without a human driver controlling it.
-
C.
autonomyStatus
chosen
Indicates the degree to which an entity operates independently or with self-governed control, without external direction or intervention.
-
D.
autonomousStatusStart
Indicates the point in time or condition at which an entity begins operating in an autonomous (self-governing or self-controlling) mode.
-
E.
isIndependent
Indicates that an entity exists, functions, or operates without being controlled, influenced, or determined by another entity.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3d757d08190a475cf47febd05ae |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a045308190ab94f3adab40db8d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.