Triple
T29838489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cranial Variation in Man |
E757718
|
entity |
| Predicate | conclusionAbout |
P61768
|
FINISHED |
| Object | continuity of human variation |
—
|
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: continuity of human variation | Statement: [Cranial Variation in Man, conclusionAbout, continuity of human variation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conclusionAbout Context triple: [Cranial Variation in Man, conclusionAbout, continuity of human variation]
-
A.
concludesAbout
chosen
Indicates that one entity forms or states a conclusion regarding another entity or its properties.
-
B.
conclusionType
Indicates the specific kind or category of conclusion associated with an argument, inference, or reasoning process.
-
C.
concludes
Indicates that one entity brings something (such as an event, process, or discussion) to an end or reaches a final decision or judgment about it.
-
D.
conclusionPosition
Indicates the position or location where a conclusion appears within a larger structure, sequence, or document.
-
E.
typicalConclusion
Indicates that one entity is the usual or expected outcome, result, or ending that follows from another entity or situation.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6760847b48190a5f0548f87faf055 |
completed | May 2, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:38 p.m.