Triple
T31544630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | red nucleus |
E804841
|
entity |
| Predicate | projectsVia |
P99887
|
FINISHED |
| Object | central tegmental tract |
—
|
NE NERFINISHED |
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: central tegmental tract | Statement: [red nucleus, projectsVia, central tegmental tract]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectsVia Context triple: [red nucleus, projectsVia, central tegmental tract]
-
A.
projectsOn
chosen
Indicates that one entity casts, directs, or extends itself onto the surface, area, or domain of another entity.
-
B.
projectsBetween
Indicates a relationship where something is projected or extends from one entity to another across an intervening space or set of entities.
-
C.
portfolioOf
Indicates that one entity is the collection of investments, works, or assets that are owned, managed, or represented by another entity.
-
D.
productionProject
Indicates that an entity is involved in or associated with a specific production project, typically as part of its creation, development, or execution.
-
E.
collaborativeProjects
Indicates that two or more entities work together on shared projects or initiatives toward common goals.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:07 p.m.