Triple
T4031841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5ESS switch |
E83730
|
entity |
| Predicate | supportsTrunks |
P53550
|
FINISHED |
| Object | T1 |
—
|
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: T1 | Statement: [5ESS switch, supportsTrunks, T1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTrunks Context triple: [5ESS switch, supportsTrunks, T1]
-
A.
hasTrunk
Indicates that one entity possesses or is equipped with a trunk as a physical feature or component.
-
B.
sharesTrunkWith
Indicates that two entities have a common trunk or main stem from which they both extend or branch.
-
C.
trunkCharacteristic
Indicates a relationship where a specific characteristic or property is attributed to a trunk (such as that of a tree or similar object).
-
D.
supportsChassisType
Indicates that one entity is compatible with and can be used to support or accommodate a specified chassis type.
-
E.
supportsVehicle
Indicates that one entity provides the necessary strength, stability, or structure to bear the weight of a vehicle.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb0f776881909db6b7df1db7664c |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fe440c819093a7fa22c4ff3f1a |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa815f2c8190818c9ffd9d1bf478 |
completed | March 9, 2026, 4:51 p.m. |
Created at: March 9, 2026, 3:36 p.m.