Triple
T32216410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European route E-road |
E822935
|
entity |
| Predicate | hasSignContent |
P179211
|
FINISHED |
| Object | letter E followed by route number |
—
|
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: letter E followed by route number | Statement: [European route E-road, hasSignContent, letter E followed by route number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignContent Context triple: [European route E-road, hasSignContent, letter E followed by route number]
-
A.
hasSign
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
B.
hasSignCode
chosen
Indicates that an entity is associated with a specific sign identifier or code used to represent it.
-
C.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
D.
haveSigned
Indicates that an entity has completed and formally agreed to a document, contract, or agreement by signing it.
-
E.
hasSignProperty
Indicates that an entity possesses a specific sign-related characteristic or attribute.
- 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_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 1, 2026, 12:37 a.m.