Triple
T29692415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D2280 |
E751245
|
entity |
| Predicate | anatomicalElement |
P45022
|
FINISHED |
| Object | cranium |
—
|
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: cranium | Statement: [D2280, anatomicalElement, cranium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anatomicalElement Context triple: [D2280, anatomicalElement, cranium]
-
A.
anatomicalFeature
chosen
Indicates that one entity is an anatomical part, structure, or feature of another entity.
-
B.
anatomicalDetail
Indicates a relationship where one entity provides specific anatomical information or finer structural characterization about another entity.
-
C.
anatomicalType
Indicates that one entity is classified as a specific anatomical category or kind of anatomical structure in relation to another.
-
D.
anatomicalMainGroup
Indicates that one anatomical structure belongs to or is classified under a primary anatomical grouping or system.
-
E.
anatomicalEvidence
Indicates that one entity provides anatomical support, features, or structures that serve as evidence for the existence, function, or characterization of 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6729570ac819095ce1c4e2ffd5971 |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:17 p.m.