Triple
T27591367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linkerd |
E699794
|
entity |
| Predicate | dataPlaneProxy |
P162726
|
FINISHED |
| Object | linkerd2-proxy |
—
|
NE NERFINISHED |
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: linkerd2-proxy | Statement: [Linkerd, dataPlaneProxy, linkerd2-proxy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataPlaneProxy Context triple: [Linkerd, dataPlaneProxy, linkerd2-proxy]
-
A.
dataPlaneType
Indicates the type or category of data plane through which data traffic or operations are carried out in a system or network.
-
B.
switchingFabric
Indicates a relationship where data traffic is routed or switched between multiple endpoints through an intermediate switching infrastructure.
-
C.
switchPortPublisher
Indicates that one entity functions as the publisher or source of data/events for a given switch port.
-
D.
pilotNetwork
Indicates that one entity operates, manages, or serves as the pilot for a network associated with another entity.
-
E.
networkPortUsage
Indicates how a specific network port is being utilized, including its activity, purpose, or traffic characteristics within a network.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63053ce0c819092673aa6b3ea8bdd |
completed | May 2, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d14c24c81909e86678c1b5fd429 |
completed | May 2, 2026, 4:57 p.m. |
Created at: April 27, 2026, 2:05 p.m.