Triple
T31754650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venetian gondola |
E810524
|
entity |
| Predicate | hasNavigationStyle |
P164895
|
FINISHED |
| Object | standing rower |
—
|
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: standing rower | Statement: [Venetian gondola, hasNavigationStyle, standing rower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavigationStyle Context triple: [Venetian gondola, hasNavigationStyle, standing rower]
-
A.
hasNavigationCharacteristic
Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
-
B.
navigationStyle
chosen
Indicates how an entity is configured or designed to guide movement, orientation, or traversal within a space or interface.
-
C.
hasNavigationStatus
Indicates the current state or condition of an entity’s navigation, such as whether and how it is actively navigating.
-
D.
hasNavigationControl
Indicates that one entity possesses authority or capability to direct, manage, or influence the movement or course of another entity.
-
E.
hasNavigationClass
Indicates that an entity is assigned to, or associated with, a particular navigation-related classification or category.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: April 30, 2026, 11:29 p.m.