Triple
T4031839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5ESS switch |
E83730
|
entity |
| Predicate | supportsLineTypes |
P47205
|
FINISHED |
| Object | analog subscriber lines |
—
|
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: analog subscriber lines | Statement: [5ESS switch, supportsLineTypes, analog subscriber lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLineTypes Context triple: [5ESS switch, supportsLineTypes, analog subscriber lines]
-
A.
lineType
Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
-
B.
servesLineType
chosen
Indicates that a service or entity operates or supports a specific type or category of line (e.g., transport, communication, or utility line).
-
C.
servedLineType
Indicates the type or category of service line associated with or provided in a given context.
-
D.
usesLineCharacteristic
Indicates that one entity employs or is based on a specific characteristic or property of a line.
-
E.
hasStraightLines
Indicates that the related entity possesses or is characterized by straight, non-curved lines.
- 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_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. |
Created at: March 9, 2026, 3:36 p.m.