Triple
T34541932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nftables |
E886826
|
entity |
| Predicate | stableSupportIn |
P48616
|
FINISHED |
| Object | Linux kernel 3.18 |
—
|
NE NERFINISHED |
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: Linux kernel 3.18 | Statement: [nftables, stableSupportIn, Linux kernel 3.18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stableSupportIn Context triple: [nftables, stableSupportIn, Linux kernel 3.18]
-
A.
supportedIn
chosen
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
B.
supportStyle
Indicates the manner or approach by which one entity provides assistance or backing to another.
-
C.
compatibleStand
Indicates that one entity can be properly supported or held by another entity’s stand or mounting system.
-
D.
supportedAfter
Indicates that one entity provided support to another only after a specified event, time, or condition had occurred.
-
E.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:02 a.m.