Triple
T34682618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puch Maxi |
E890658
|
entity |
| Predicate | fuelTankPosition |
P126038
|
FINISHED |
| Object | under seat or top tube |
—
|
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: under seat or top tube | Statement: [Puch Maxi, fuelTankPosition, under seat or top tube]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelTankPosition Context triple: [Puch Maxi, fuelTankPosition, under seat or top tube]
-
A.
fuelTankConfiguration
Indicates how a system’s fuel tanks are arranged, connected, or structured relative to one another.
-
B.
fuelLocation
chosen
Indicates the place or source where fuel is stored, supplied, or located for use.
-
C.
fuelCondition
Indicates the state or quality of fuel associated with an entity, such as its level, usability, or readiness for operation.
-
D.
hasTankPosition
Indicates that an entity occupies or is assigned to a specific tank position or location.
-
E.
fuelTransferLocation
Indicates the place or facility where fuel is transferred from one container, vehicle, or system to another.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7232925e48190b6ecd37927325057 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.