Triple
T29692500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skull 5 |
E751247
|
entity |
| Predicate | hasCraniumComplete |
P178315
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Skull 5, hasCraniumComplete, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCraniumComplete Context triple: [Skull 5, hasCraniumComplete, true]
-
A.
hasSkull
Indicates that an entity possesses or is characterized by the presence of a skull.
-
B.
hasCranialCapacity
Indicates that one entity possesses a specific volume or size of space within the skull available for the brain.
-
C.
hasSkullFeature
Indicates that an entity possesses a specific characteristic, structure, or attribute of the skull.
-
D.
hasSkullType
Indicates that an entity possesses or is characterized by a specific type or classification of skull.
-
E.
hasSkullDisplayedSeparately
Indicates that the skull of an individual or specimen is displayed separately from the rest of its remains or body.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 28, 2026, 7:18 p.m.