Triple
T26726717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISI ResearchSoft |
E673854
|
entity |
| Predicate | servedDomain |
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: [ISI ResearchSoft, servedDomain, academic research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedDomain Context triple: [ISI ResearchSoft, servedDomain, academic research]
-
A.
domainServed
chosen
Indicates that a particular domain or area is supported, covered, or provided for by a given entity or service.
-
B.
servedFrom
Indicates that something is provided, delivered, or made available from a particular source or location.
-
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.
laterDomain
Indicates that one domain or time interval occurs strictly after another in a temporal ordering.
-
E.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 27, 2026, 3:43 a.m.