Triple
T15108403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10gen |
E360846
|
entity |
| Predicate | soughtToCompeteWith |
P1375
|
FINISHED |
| Object | relational database vendors |
—
|
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: relational database vendors | Statement: [10gen, soughtToCompeteWith, relational database vendors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soughtToCompeteWith Context triple: [10gen, soughtToCompeteWith, relational database vendors]
-
A.
competesWith
chosen
Indicates that two entities are in rivalry or opposition, each striving to outperform or gain advantage over the other in the same domain or objective.
-
B.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
C.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
-
D.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
E.
competedFor
Indicates that an entity took part in a contest, rivalry, or competition in pursuit of another entity (such as a prize, position, 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0058af8988190977d998f85893836 |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:05 a.m.