Triple
T249983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pan troglodytes |
E5120
|
entity |
| Predicate | averageHeadBodyLength |
P3593
|
FINISHED |
| Object | 63–94 cm |
—
|
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: 63–94 cm | Statement: [Pan troglodytes, averageHeadBodyLength, 63–94 cm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: averageHeadBodyLength Context triple: [Pan troglodytes, averageHeadBodyLength, 63–94 cm]
-
A.
averageWeight
Indicates the typical or mean weight value associated with an entity or group of entities.
-
B.
bodySize
chosen
Indicates the relative physical magnitude or scale of an entity’s body, such as how large or small it is.
-
C.
highestBody
Indicates that one entity is the tallest or most elevated body (e.g., physical object, celestial body, or structural component) relative to a specified set or context.
-
D.
hasSmallBodyPopulation
Indicates that an entity has a relatively low number of small celestial bodies (such as asteroids, comets, or minor planets) associated with it.
-
E.
wingspan
Indicates the distance from the tip of one wing to the tip of the other wing when fully extended.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d3728f0819086214ccc2db2305a |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b665f8c8190aac6fcbba2a0eebb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.