Triple
T28508141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zenmap |
E721413
|
entity |
| Predicate | officialGUIFor |
P66728
|
FINISHED |
| Object | Nmap |
—
|
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: Nmap | Statement: [Zenmap, officialGUIFor, Nmap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialGUIFor Context triple: [Zenmap, officialGUIFor, Nmap]
-
A.
officialToolFor
chosen
Indicates that one entity is formally designated or authorized as the standard or primary tool to be used for another entity or purpose.
-
B.
officialScriptOf
Indicates that one writing system is formally designated as the standard or legally recognized script used for a particular language, region, or entity.
-
C.
officialAdapterFor
Indicates that one entity serves as the formally designated adapter or intermediary component for another entity.
-
D.
officialRepositoryFor
Indicates that one entity serves as the primary, authoritative repository or source for another entity.
-
E.
isOfficialPortalFor
Indicates that one entity serves as the recognized, authoritative portal or entry point for accessing information or services related to 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 28, 2026, 3:10 a.m.