Triple
T25642703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RethinkDB |
E642874
|
entity |
| Predicate | hasAdminInterface |
P163843
|
FINISHED |
| Object | web dashboard |
—
|
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: web dashboard | Statement: [RethinkDB, hasAdminInterface, web dashboard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdminInterface Context triple: [RethinkDB, hasAdminInterface, web dashboard]
-
A.
hasAdministrationMethod
Indicates the method or route by which something (typically a drug, treatment, or resource) is administered or delivered.
-
B.
isAdministeredOn
Indicates that an action, treatment, or procedure is given or applied to a subject at a specific time or date.
-
C.
isAdministeredFor
Indicates that a treatment, medication, or intervention is given or applied for the purpose of addressing a particular condition, need, or intended outcome.
-
D.
hasAdministrationSite
Indicates the specific location or site on or in a subject where a substance, treatment, or intervention is administered.
-
E.
isAdministeredThrough
Indicates that something (such as a treatment, service, or process) is delivered or carried out via a particular method, route, or medium.
- F. None of above. chosen
Provenance (4 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 21, 2026, 5:46 p.m.