Triple
T30720448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PPP |
E782141
|
entity |
| Predicate | supportsMultilink |
P56779
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [PPP, supportsMultilink, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMultilink Context triple: [PPP, supportsMultilink, yes]
-
A.
supportsLinkAggregation
chosen
Indicates that one entity provides or is compatible with link aggregation capabilities for combining multiple network connections into a single logical link.
-
B.
supportsAirLink
Indicates that one entity is capable of establishing or maintaining an AirLink wireless connection with another entity.
-
C.
supportsLinks
Indicates that one entity provides backing, endorsement, or assistance to another entity through connections or references (such as hyperlinks or relational links).
-
D.
hasLinkCableSupport
Indicates that one entity supports being connected to another via a link cable for interaction or data exchange.
-
E.
supportsMultipleTerminals
Indicates that an entity is capable of handling or operating with more than one terminal or endpoint simultaneously.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:36 p.m.