Triple
T27945852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NetBIOS API |
E700876
|
entity |
| Predicate | exposesConcept |
P463
|
FINISHED |
| Object | NetBIOS name |
—
|
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: NetBIOS name | Statement: [NetBIOS API, exposesConcept, NetBIOS name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exposesConcept Context triple: [NetBIOS API, exposesConcept, NetBIOS name]
-
A.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
B.
demonstratedConcept
chosen
Indicates that an entity has shown, illustrated, or made evident a particular concept through example, explanation, or action.
-
C.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
D.
exportsConcept
Indicates that one entity sends or supplies a concept, idea, or abstract knowledge resource from itself to another entity or context.
-
E.
providesExposureTo
Indicates that one entity gives another entity the opportunity to be seen, noticed, or become known by a particular audience, environment, or set of influences.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 7:22 p.m.