Triple
T26345670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semantic Web agents |
E662771
|
entity |
| Predicate | canUseOntology |
P9928
|
FINISHED |
| Object | application ontology |
—
|
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: application ontology | Statement: [Semantic Web agents, canUseOntology, application ontology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canUseOntology Context triple: [Semantic Web agents, canUseOntology, application ontology]
-
A.
canUse
chosen
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
B.
canBeUsed
Indicates that one entity is suitable or available to serve a particular function, purpose, or role in relation to another entity or context.
-
C.
isIntendedForUseBy
Indicates that something is designed, meant, or purposed to be used by a particular entity or group.
-
D.
useOfTerm
Indicates that one entity employs or applies a specific term or expression in reference to another entity or context.
-
E.
assessesForUseIn
Indicates that one entity evaluates another entity to determine its suitability or appropriateness for a particular use or application.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fa718188190a3f4d76db2cdf670 |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 10:41 p.m.