Triple
T2181142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission Bay |
E49043
|
entity |
| Predicate | primaryResearchArea |
P19488
|
FINISHED |
| Object | biomedical sciences |
—
|
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: biomedical sciences | Statement: [Mission Bay, primaryResearchArea, biomedical sciences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryResearchArea Context triple: [Mission Bay, primaryResearchArea, biomedical sciences]
-
A.
hasResearchArea
Indicates that an entity (such as a person, project, or organization) is associated with or focused on a particular field or area of research.
-
B.
researchTopic
Indicates that a subject conducts or focuses research on a particular topic or area of study.
-
C.
researchClassification
Indicates that an entity is assigned a specific category or type within a research-related classification scheme.
-
D.
primaryResearchLibraryFor
Indicates that one entity serves as the main or principal research library resource for another entity.
-
E.
primaryArea
chosen
Indicates that one entity is the main or most important area, domain, or field associated with another entity.
- 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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc4358fc88190a6f556c2de9fef8c |
completed | March 7, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69abbda0ec948190be88c1243d81a423 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.