Triple
T27271167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo rudolfensis |
E688054
|
entity |
| Predicate | braincaseSize |
P3593
|
FINISHED |
| Object | relatively large for its time |
—
|
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: relatively large for its time | Statement: [Homo rudolfensis, braincaseSize, relatively large for its time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: braincaseSize Context triple: [Homo rudolfensis, braincaseSize, relatively large for its time]
-
A.
typicalCaseDiameter
Indicates the usual or standard diameter value associated with an object or case in typical conditions.
-
B.
bodySize
chosen
Indicates the relative physical magnitude or scale of an entity’s body, such as how large or small it is.
-
C.
sizeType
Indicates the kind or category of size associated with an entity, such as relative scale, measurement type, or size classification.
-
D.
modelSize
Indicates the quantitative measure of how large or complex a model is, typically in terms of parameters, layers, or memory footprint.
-
E.
bellSize
Indicates a relationship where an entity is characterized or classified by the size of a bell associated with it.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f62722eba88190b66a514b023a1197 |
completed | May 2, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 10:59 a.m.