Triple
T7115495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OBDA systems |
E165807
|
entity |
| Predicate | useComponent |
P9772
|
FINISHED |
| Object | 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: ontology | Statement: [OBDA systems, useComponent, ontology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useComponent Context triple: [OBDA systems, useComponent, ontology]
-
A.
usedComponent
chosen
Indicates that one entity has employed or incorporated another entity as a component in its structure, function, or operation.
-
B.
componentFrom
Indicates that one entity is derived from, produced by, or originates as a component of another entity.
-
C.
componentElement
Indicates that one entity is a constituent or part of another, larger entity or structure.
-
D.
definesComponent
Indicates that one entity specifies or establishes the structure, behavior, or characteristics of another entity as its component.
-
E.
replacesComponentOf
Indicates that one entity takes the place of a specific component within another entity, substituting for that component in its role or function.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5f401b881909ef4c2ab1e0750db |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.