Triple
T28998367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM VSE |
E736224
|
entity |
| Predicate | typicalIndustryUse |
P198113
|
FINISHED |
| Object | banking |
—
|
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: banking | Statement: [IBM VSE, typicalIndustryUse, banking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalIndustryUse Context triple: [IBM VSE, typicalIndustryUse, banking]
-
A.
usedInIndustry
Indicates that something is employed or applied within a particular industry or industrial sector.
-
B.
typicalSectorUse
Indicates the type of sector in which something is most commonly or characteristically used.
-
C.
hasTypicalIndustry
chosen
Indicates that an entity is commonly or characteristically associated with a particular industry or sector.
-
D.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
E.
constructionUses
Indicates that a construction activity, project, or structure makes use of a specified material, method, tool, or resource.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a0144c75aec81908bdd9e88f2af737a |
completed | May 11, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_6a014405a2d48190a1d58b0b907ad696 |
completed | May 11, 2026, 2:50 a.m. |
Created at: April 28, 2026, 9:33 a.m.