Triple
T957697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thread |
E20659
|
entity |
| Predicate | supportsAddressing |
P3704
|
FINISHED |
| Object | IPv6 unicast |
—
|
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: IPv6 unicast | Statement: [Thread, supportsAddressing, IPv6 unicast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAddressing Context triple: [Thread, supportsAddressing, IPv6 unicast]
-
A.
supportsAddressTypes
chosen
Indicates that an entity is capable of handling or working with one or more specified types of addresses.
-
B.
usesAddressingSystem
Indicates that one entity employs or applies a particular addressing system associated with another entity.
-
C.
hasAddress
Indicates that an entity is associated with a specific address or location.
-
D.
addressedBy
Indicates that something (such as an issue, request, or item) is handled, dealt with, or responded to by a particular agent or entity.
-
E.
supportsPosition
Indicates that one entity endorses, upholds, or provides backing for the stance, viewpoint, or role represented by another entity.
- 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3fac2bc8190a66feb70c68899b2 |
completed | March 1, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a18ecc8190883f6206fe3b0fb6 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.