Triple
T34541996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | POSTROUTING |
E886827
|
entity |
| Predicate | hookNumber |
P179291
|
FINISHED |
| Object | NF_INET_POST_ROUTING |
—
|
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: NF_INET_POST_ROUTING | Statement: [POSTROUTING, hookNumber, NF_INET_POST_ROUTING]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hookNumber Context triple: [POSTROUTING, hookNumber, NF_INET_POST_ROUTING]
-
A.
hookType
Indicates the specific kind or category of hook associated with or used by an entity.
-
B.
hookOf
Indicates that one entity functions as a hook or hooking component that is part of, attached to, or used by another entity.
-
C.
hasHook
Indicates that one entity possesses, is equipped with, or features a hook in relation to another entity or context.
-
D.
junctionNumber
Indicates the identifying number assigned to a specific junction or intersection within a network or system.
-
E.
hookPhrase
Indicates that one entity serves as a catchy or attention-grabbing phrase associated with another entity, typically used to attract interest or summarize its appeal.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: May 1, 2026, 2:02 a.m.