Triple
T23105868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MA 17 |
E576160
|
entity |
| Predicate | currentImportance |
P89351
|
FINISHED |
| Object | minor travel corridor |
—
|
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: minor travel corridor | Statement: [MA 17, currentImportance, minor travel corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentImportance Context triple: [MA 17, currentImportance, minor travel corridor]
-
A.
resultImportance
Indicates that one entity specifies how significant, critical, or impactful the outcome or result of another entity is.
-
B.
peakImportance
Indicates that something reaches or represents the highest level of importance within a given context or timeframe.
-
C.
localImportance
chosen
Indicates that something holds particular significance, influence, or priority within a specific, limited context or area rather than globally.
-
D.
isImportantFor
Indicates that something holds significant value, relevance, or necessity in relation to something else.
-
E.
nivelDeImportancia
Indicates the degree or level of importance assigned to something in relation to something else.
- 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_69e245f4af548190898d434a64a1e774 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e0ad44c81908e1873d4b3860323 |
completed | April 29, 2026, 4:50 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:58 p.m.