Triple
T27591368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linkerd |
E699794
|
entity |
| Predicate | controlPlaneLanguage |
P4197
|
FINISHED |
| Object | Go |
—
|
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: Go | Statement: [Linkerd, controlPlaneLanguage, Go]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlPlaneLanguage Context triple: [Linkerd, controlPlaneLanguage, Go]
-
A.
languageOfCommand
Indicates that a specified language is the one in which a given command is expressed or issued.
-
B.
controlPlaneType
Indicates the type or mode of control plane used to manage and coordinate the system’s components or network operations.
-
C.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
D.
languageOfOperation
chosen
Indicates the language in which an entity (such as a system, service, or process) primarily operates or functions.
-
E.
languageOfOnboardOperations
Indicates the language used to conduct or manage onboard operations.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 2:05 p.m.