Triple
T19434699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JAX-WS |
E486199
|
entity |
| Predicate | toolingExample |
P66291
|
FINISHED |
| Object | wsimport |
—
|
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: wsimport | Statement: [JAX-WS, toolingExample, wsimport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toolingExample Context triple: [JAX-WS, toolingExample, wsimport]
-
A.
toolingArea
Indicates that one entity serves as the designated area or zone where tools or tooling-related activities for the other entity are located or performed.
-
B.
includesTooling
chosen
Indicates that one entity contains, provides, or comes bundled with specific tools or tooling capabilities related to another entity.
-
C.
toolIn
Indicates that one entity is a tool or instrument used in or associated with another entity or context.
-
D.
toolUsed
Indicates that an action or task is performed using a particular tool as the means or instrument.
-
E.
toolDeveloperFor
Indicates that one entity is the creator or developer of a tool that is used by or associated with 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6335e8f7881909c8b28886521046e |
completed | April 20, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.