Triple
T28019738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gauge 1 |
E707652
|
entity |
| Predicate | supportsModelTypes |
P19966
|
FINISHED |
| Object | steam locomotives |
—
|
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: steam locomotives | Statement: [Gauge 1, supportsModelTypes, steam locomotives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsModelTypes Context triple: [Gauge 1, supportsModelTypes, steam locomotives]
-
A.
supportsModelType
chosen
Indicates that an entity is compatible with, or can operate using, a specified model type.
-
B.
supportedModel
Indicates that one entity provides compatibility with, or operational backing for, a particular model.
-
C.
supportsModelFamily
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or use of a particular model family.
-
D.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
E.
supportsModelVariant
Indicates that one entity is capable of operating with, being compatible with, or otherwise accommodating a specific variant of a model.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_6a004c41f13c8190bc47daf6a5ca3949 |
completed | May 10, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_6a004bce3e3081909b35ae5b3bf2b35e |
completed | May 10, 2026, 9:11 a.m. |
Created at: April 27, 2026, 8:09 p.m.