Triple
T26399129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VRRP |
E663651
|
entity |
| Predicate | defaultPriority |
P128025
|
FINISHED |
| Object | 100 |
—
|
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: 100 | Statement: [VRRP, defaultPriority, 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultPriority Context triple: [VRRP, defaultPriority, 100]
-
A.
priorityRule
Indicates that one entity is given precedence or higher processing order over another according to a defined rule or policy.
-
B.
priorityDeterminedBy
Indicates that the priority or importance level of one entity is established based on another entity or set of factors.
-
C.
defaultValue
chosen
Indicates that one entity serves as the pre-assigned or fallback value automatically used for another entity when no explicit value is provided.
-
D.
defaultQValue
Indicates the standard or initial Q-value assigned to a state-action pair before any learning or updates occur in a reinforcement learning process.
-
E.
supportsPriority
Indicates that one entity provides functionality or capability for handling or honoring priority levels associated with another entity or operation.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610f2c09c8190849494490f255758 |
completed | May 2, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:30 p.m.