Triple
T32216401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European route E-road |
E822935
|
entity |
| Predicate | hasLetterPrefix |
P178779
|
FINISHED |
| Object | E |
—
|
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: E | Statement: [European route E-road, hasLetterPrefix, E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLetterPrefix Context triple: [European route E-road, hasLetterPrefix, E]
-
A.
hasLetterSuffix
Indicates that an entity’s identifier, name, or code ends with a specific letter or sequence of letters.
-
B.
hasLetter
Indicates that one entity contains, includes, or is associated with a specific letter or character.
-
C.
hasLetterPattern
Indicates that one entity exhibits or matches a specific sequence or arrangement of letters defined by another entity.
-
D.
hasInitialLetters
Indicates that one entity’s initial letters or acronym are derived from or correspond to the other entity.
-
E.
hasLetterName
chosen
Indicates that an entity is associated with a specific letter used as its name or designation.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 1, 2026, 12:37 a.m.