Triple
T19039330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Jolla campus |
E465958
|
entity |
| Predicate | researchOutputType |
P218
|
FINISHED |
| Object | scientific publications |
—
|
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: scientific publications | Statement: [La Jolla campus, researchOutputType, scientific publications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: researchOutputType Context triple: [La Jolla campus, researchOutputType, scientific publications]
-
A.
researchOutcome
Indicates that an action, study, or investigation produces a specific result, finding, or conclusion.
-
B.
researchSupportType
Indicates the specific kind of support provided for research activities, such as funding, resources, or services.
-
C.
publicationType
chosen
Indicates the specific category or format of a published work that characterizes how it is issued or presented.
-
D.
publicationTypeOf
Indicates that one entity specifies the type or category of publication to which another publication entity belongs.
-
E.
researchContribution
Indicates that an entity has produced or participated in creating new knowledge, findings, or innovations within a research context.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d7ff9b6c8190adc3917a8c9af7bd |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4a3001e388190aa6057266514e75a |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.