Triple
T5350462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malayan sun bear |
E124164
|
entity |
| Predicate | bodySizeRelative |
P8238
|
FINISHED |
| Object | smallest bear species |
—
|
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: smallest bear species | Statement: [Malayan sun bear, bodySizeRelative, smallest bear species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodySizeRelative Context triple: [Malayan sun bear, bodySizeRelative, smallest bear species]
-
A.
bodySize
Indicates the relative physical magnitude or scale of an entity’s body, such as how large or small it is.
-
B.
hasRelativeSize
chosen
Indicates that one entity’s size is being compared to another entity’s size, expressing a relative rather than absolute magnitude.
-
C.
surfaceAreaRelative
Indicates the ratio or comparative measure of one entity’s surface area relative to another reference surface area.
-
D.
sizeDefinedBy
Indicates that the size or magnitude of one entity is determined, constrained, or specified by another entity.
-
E.
sizeDescription
Indicates a relationship where one entity provides descriptive information about the size or scale 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd860fe4048190846a933d0e1b9386 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.