Triple
T27945973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBT |
E700878
|
entity |
| Predicate | transportMechanismFor |
P10597
|
FINISHED |
| Object | NetBIOS API |
—
|
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 API | Statement: [NBT, transportMechanismFor, NetBIOS API]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportMechanismFor Context triple: [NBT, transportMechanismFor, NetBIOS API]
-
A.
transitionMechanismUsedWith
Indicates that a particular transition or change from one state to another is carried out using a specified mechanism or method.
-
B.
transportInterface
Indicates a relationship where one entity serves as the medium or mechanism through which another entity is transported or conveyed.
-
C.
transportLayerFor
chosen
Indicates that one entity functions as the transport-layer protocol or mechanism used to carry or deliver another entity’s data.
-
D.
transportAgnostic
Indicates that the relationship or action is independent of, and unaffected by, the specific transport mechanism or communication channel used.
-
E.
transportFor
Indicates a relationship where one entity serves as the means or service used to move another entity from one place to another.
- 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_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 27, 2026, 7:22 p.m.