Triple
T29986521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | open science movement |
E761748
|
entity |
| Predicate | targetsDomain |
P60634
|
FINISHED |
| Object | academic research |
—
|
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: academic research | Statement: [open science movement, targetsDomain, academic research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsDomain Context triple: [open science movement, targetsDomain, academic research]
-
A.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
-
B.
containsDomain
Indicates that one entity includes or encompasses a specific domain as part of its scope, structure, or area of applicability.
-
C.
indicatesDomain
Indicates a domain or area of knowledge, activity, or applicability to which something (such as a concept, resource, or entity) belongs or is relevant.
-
D.
domainServed
chosen
Indicates that a particular domain or area is supported, covered, or provided for by a given entity or service.
-
E.
laterDomain
Indicates that one domain or time interval occurs strictly after another in a temporal ordering.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 29, 2026, 6:36 p.m.