Triple
T26398990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Label Distribution Protocol |
E663648
|
entity |
| Predicate | discoversNeighborsUsing |
P64012
|
FINISHED |
| Object | LDP Hello messages |
—
|
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: LDP Hello messages | Statement: [Label Distribution Protocol, discoversNeighborsUsing, LDP Hello messages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoversNeighborsUsing Context triple: [Label Distribution Protocol, discoversNeighborsUsing, LDP Hello messages]
-
A.
usesNeighborDiscovery
chosen
Indicates that an entity employs a neighbor discovery mechanism to detect, identify, or maintain information about adjacent or nearby entities in a network or environment.
-
B.
hasNearbyDiscovery
Indicates that one entity has a discovery located in close physical or spatial proximity to it.
-
C.
inUniverseNeighbor
Indicates that two entities are neighbors within the same fictional or defined universe or setting.
-
D.
outerNeighbor
Indicates that one entity is adjacent to another from the outside, typically sharing a boundary but not being contained within it.
-
E.
innerNeighbor
Indicates that one entity is directly adjacent to another entity on the inside or interior side of a boundary or structure.
- 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_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 26, 2026, 11:30 p.m.