Triple
T8755820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YANG actions |
E208069
|
entity |
| Predicate | supportUseCase |
P15794
|
FINISHED |
| Object | resetting a specific interface |
—
|
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: resetting a specific interface | Statement: [YANG actions, supportUseCase, resetting a specific interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportUseCase Context triple: [YANG actions, supportUseCase, resetting a specific interface]
-
A.
supportsUse
chosen
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
B.
support
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
-
C.
supportStyle
Indicates the manner or approach by which one entity provides assistance or backing to another.
-
D.
supportBase
Indicates that one entity serves as a foundational or backing structure that physically or functionally supports another entity.
-
E.
supportAgainst
Indicates providing help, resources, or advocacy to oppose or resist a particular target, threat, or adversary.
- 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5dd95e9481909cc88e8d91601754 |
completed | March 31, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.