Triple
T27348144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | arcuate fasciculus |
E684282
|
entity |
| Predicate | isAlsoFoundIn |
P162209
|
FINISHED |
| Object | nonhuman primates |
—
|
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: nonhuman primates | Statement: [arcuate fasciculus, isAlsoFoundIn, nonhuman primates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAlsoFoundIn Context triple: [arcuate fasciculus, isAlsoFoundIn, nonhuman primates]
-
A.
discoveredAsPartOf
Indicates that something was found, identified, or revealed in the course of a larger activity, process, or investigation of which it formed a component.
-
B.
isAlsoUsedAs
Indicates that something serves an additional function or role beyond its primary one.
-
C.
wasDiscoveredIn
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
D.
alsoUsedIn
Indicates that something is additionally employed, applied, or present in another context, setting, or use case beyond the primary one.
-
E.
alsoExpressedIn
Indicates that something which is expressed in one context, medium, or entity is likewise expressed in another.
- F. None of above. chosen
Provenance (4 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62ba5a110819092fe773ade8fec2e |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 27, 2026, 11:46 a.m.