Triple
T13532060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Division |
E323155
|
entity |
| Predicate | isPhysicallyIncompatibleWith |
P16201
|
FINISHED |
| Object | B Division rolling stock |
—
|
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: B Division rolling stock | Statement: [A Division, isPhysicallyIncompatibleWith, B Division rolling stock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPhysicallyIncompatibleWith Context triple: [A Division, isPhysicallyIncompatibleWith, B Division rolling stock]
-
A.
notCompatibleWith
chosen
Indicates that two entities cannot function together properly or are unsuitable for joint use or interaction.
-
B.
mechanicalCompatibility
Indicates that two entities can function together properly from a mechanical standpoint, without interference, damage, or performance issues.
-
C.
isGenerallyCompatibleWith
Indicates that two entities can typically function or coexist together without significant conflict, issues, or need for special adaptation.
-
D.
compatibleSign
Indicates that two entities are considered astrologically harmonious or well-matched based on their zodiac signs.
-
E.
compatibleStand
Indicates that one entity can be properly supported or held by another entity’s stand or mounting system.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafbb34548190a6b44faa48125cd4 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.