Triple
T7115520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OBDA systems |
E165807
|
entity |
| Predicate | distinguishFrom |
P6335
|
FINISHED |
| Object | traditional data warehousing |
—
|
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: traditional data warehousing | Statement: [OBDA systems, distinguishFrom, traditional data warehousing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distinguishFrom Context triple: [OBDA systems, distinguishFrom, traditional data warehousing]
-
A.
isDistinctFrom
Indicates that two entities are not identical and can be clearly distinguished from one another.
-
B.
categoryDistinguishedFrom
Indicates that one category is explicitly distinguished from another, clarifying that they are separate and should not be confused.
-
C.
differentiatedFrom
chosen
Indicates that one entity is distinguished or set apart from another by identifying differences between them.
-
D.
distinction
Indicates that one entity is recognized, treated, or classified as different or separate from another.
-
E.
isDistinguishedBy
Indicates that one entity is characterized or set apart from others by a particular feature, quality, or attribute.
- 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.