Triple
T3612864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eureka |
E76528
|
entity |
| Predicate | paddleConfiguration |
P49950
|
FINISHED |
| Object | side-wheel |
—
|
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: side-wheel | Statement: [Eureka, paddleConfiguration, side-wheel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paddleConfiguration Context triple: [Eureka, paddleConfiguration, side-wheel]
-
A.
defaultConfigurationTool
Indicates that one tool is designated as the standard or primary utility used for configuring another system or component.
-
B.
portConfiguration
Indicates how ports are arranged, assigned, or set up for use within a system or device.
-
C.
advancedConfigurationTool
Indicates that an entity functions as a sophisticated tool or system used to manage or modify complex configuration settings or parameters.
-
D.
configuration
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
-
E.
passengerConfiguration
Indicates how passengers are arranged, seated, or distributed within a vehicle or transport setting.
- 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2786f808190be4e42734a79d74e |
completed | March 8, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb8e4ba948190a9b777cf7f788b96 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:23 p.m.