Triple
T3369652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | spectacled flying fox |
E70921
|
entity |
| Predicate | forearmLength |
P47639
|
FINISHED |
| Object | approximately 16 to 18 centimetres |
—
|
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: approximately 16 to 18 centimetres | Statement: [spectacled flying fox, forearmLength, approximately 16 to 18 centimetres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forearmLength Context triple: [spectacled flying fox, forearmLength, approximately 16 to 18 centimetres]
-
A.
armType
Indicates the specific kind or configuration of an arm associated with an entity.
-
B.
isForwardArmOf
Indicates that one object functions as the front or leading arm/extension of another object in a given structure or system.
-
C.
frontLength
Indicates the length measurement of the front side or edge of an object relative to its overall dimensions.
-
D.
hasArms
Indicates that an entity possesses arms as physical appendages.
-
E.
hasArm
Indicates that one entity possesses or is equipped with an arm as a physical part or component of itself.
- 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_69ad85a729d48190afd789cd8417f289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2b9b1fc8190a2cbf040ea808baf |
completed | March 8, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ada4317e288190ab7d0f66e9dba65f |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada698eeb48190a1f5762fdd3b7b63 |
completed | March 8, 2026, 4:40 p.m. |
Created at: March 8, 2026, 3:13 p.m.