Triple
T18899689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sentinelle Rouge route |
E462302
|
entity |
| Predicate | hasCommitmentLevel |
P27619
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Sentinelle Rouge route, hasCommitmentLevel, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommitmentLevel Context triple: [Sentinelle Rouge route, hasCommitmentLevel, high]
-
A.
commitmentGrade
chosen
Indicates the level or quality of commitment one entity has made toward another entity or agreed-upon action.
-
B.
hasObligationLevel
Indicates that one entity bears a specified degree or intensity of duty, responsibility, or required action toward another entity or situation.
-
C.
hasConditionalityLevel
Indicates that one entity is associated with a specific degree or level of conditional requirements, constraints, or dependencies relative to another entity or context.
-
D.
coreCommitment
Indicates a fundamental, central obligation or promise that defines the primary responsibility or dedication within a relationship or agreement.
-
E.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c5289ba48190a6825c4db2e5e48d |
completed | April 20, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.