Triple
T19582739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cisco Discovery Protocol |
E490035
|
entity |
| Predicate | defaultHoldtimeSeconds |
P136342
|
FINISHED |
| Object | 180 |
—
|
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: 180 | Statement: [Cisco Discovery Protocol, defaultHoldtimeSeconds, 180]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultHoldtimeSeconds Context triple: [Cisco Discovery Protocol, defaultHoldtimeSeconds, 180]
-
A.
heldByUntil
Indicates that an entity maintains possession or control of something up to, but not necessarily beyond, a specified time or condition.
-
B.
firstHolderLifespan
Indicates the duration of life of the initial holder in a sequence of holders.
-
C.
heldUntil
Indicates that a state, condition, or action continues to hold true up to a specified time or event, and may cease to hold immediately after that point.
-
D.
firstHeldFor
Indicates the initial time period or event during which an entity was first held, possessed, or hosted by another entity.
-
E.
recordHeldUntil
Indicates that a record remained valid, in force, or applicable up to a specified end time or condition.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6404e18f88190b7fec59499dd25e8 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:42 p.m.