Triple
T36957923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doom game engine |
E914234
|
entity |
| Predicate | spawnedPorts |
P186803
|
FINISHED |
| Object | numerous source ports |
—
|
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: numerous source ports | Statement: [Doom game engine, spawnedPorts, numerous source ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spawnedPorts Context triple: [Doom game engine, spawnedPorts, numerous source ports]
-
A.
servedPorts
Indicates that a network service or device makes specific ports available to accept incoming connections or traffic.
-
B.
executionPorts
Indicates a relationship where specific ports are used as the channels or endpoints through which an execution or process is carried out.
-
C.
openedPorts
Indicates that a network host has specific communication ports currently open and available for connections.
-
D.
openedPorts
Indicates that certain network ports on a host or device are currently open and accepting connections.
-
E.
hasPorts
Indicates that an entity is equipped with or provides access points (ports) for connection, communication, or interface with other entities or systems.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:13 p.m.