Triple
T19352194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethereal |
E484049
|
entity |
| Predicate | captureSource |
P110259
|
FINISHED |
| Object | network interfaces |
—
|
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: network interfaces | Statement: [Ethereal, captureSource, network interfaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captureSource Context triple: [Ethereal, captureSource, network interfaces]
-
A.
captureType
Indicates the manner or method by which something is captured, recorded, or acquired in the context of the relationship.
-
B.
samplingSource
chosen
Indicates that one entity serves as the origin or provider from which another entity is sampled or drawn.
-
C.
capturedFrom
Indicates that one entity has taken possession or control of another entity away from a specified source or previous holder.
-
D.
electronSource
Indicates a relationship where one entity serves as the origin or provider of electrons for another entity or process.
-
E.
capturedUsing
Indicates that something was recorded, obtained, or documented by means of a specified tool, method, or device.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61905b16881909ab0e932bb9a0cda |
completed | April 20, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e4dd13a8cc81909cd02668564c9f29 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.