Triple
T26848720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cab Forward |
E675994
|
entity |
| Predicate | lessSuitedFor |
P79409
|
FINISHED |
| Object | coal firing due to cab-forward arrangement |
—
|
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: coal firing due to cab-forward arrangement | Statement: [Cab Forward, lessSuitedFor, coal firing due to cab-forward arrangement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lessSuitedFor Context triple: [Cab Forward, lessSuitedFor, coal firing due to cab-forward arrangement]
-
A.
lessSuitableFor
chosen
Indicates that one entity is comparatively less appropriate, effective, or fitting than another for a given purpose, context, or condition.
-
B.
isSuitableFor
Indicates that one entity is appropriate, fitting, or well-matched for use, application, or association with another entity.
-
C.
isPerfectFor
Indicates that one entity is ideally suited or optimally appropriate for another entity, purpose, or context.
-
D.
lessWorthyThan
Indicates that one entity is considered to have lower value, merit, or worth compared to another entity.
-
E.
notSufficientFor
Indicates that the presence or occurrence of one condition does not by itself guarantee or bring about the other condition.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61b90393c819090595eac8e538e05 |
completed | May 2, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:14 a.m.