Triple
T16140442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vizzavona |
E391638
|
entity |
| Predicate | roleOnGR20 |
P121259
|
FINISHED |
| Object | major stopover point |
—
|
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: major stopover point | Statement: [Vizzavona, roleOnGR20, major stopover point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOnGR20 Context triple: [Vizzavona, roleOnGR20, major stopover point]
-
A.
roleOnIsland
Indicates the specific function, position, or responsibility an entity holds within the context of an island.
-
B.
rangeRole
Indicates that the specified role is associated with, or applies to, the range (target) of a property or relationship.
-
C.
roleOnAtlasV
Indicates that an entity holds a specific role or function in relation to the Atlas V launch vehicle or program.
-
D.
roleWithLAT
Indicates a relationship where an entity holds or is associated with a specific role that is characterized or constrained by a particular location, attribute, or type (LAT).
-
E.
roleAtMidway
Indicates that an entity holds or held a specific role, position, or function at the midpoint or intermediate stage of a process, event, or time period.
- F. None of above. chosen
Provenance (4 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a07b7908190b4e1ec57f60a9274 |
completed | April 17, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1835b64948190ae1d2a9d4cc64acf |
completed | April 17, 2026, 12:48 a.m. |
Created at: April 10, 2026, 5:01 a.m.