Triple
T16302899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wankel rotary engine |
E395833
|
entity |
| Predicate | hasHousingShape |
P122601
|
FINISHED |
| Object | epitrochoid |
—
|
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: epitrochoid | Statement: [Wankel rotary engine, hasHousingShape, epitrochoid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHousingShape Context triple: [Wankel rotary engine, hasHousingShape, epitrochoid]
-
A.
hasFloorPlanShape
Indicates that an entity has a specific geometric or structural configuration defining the shape of its floor plan.
-
B.
hasHousingArrangement
Indicates that an entity has a specific type or status of housing or living arrangement in relation to another entity or context.
-
C.
hasRoofShape
Indicates that one entity possesses or is characterized by a specific shape or form of roof.
-
D.
hasHousingUnits
Indicates that an entity possesses or contains a specified number or set of housing units.
-
E.
housingPattern
Indicates the typical arrangement or distribution of housing units or residential structures within a given area or context.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e3404288190a7106d62c15c3193 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:06 a.m.