Triple
T21643173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rousettus |
E534145
|
entity |
| Predicate | echolocationType |
P28101
|
FINISHED |
| Object | rudimentary echolocation |
—
|
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: rudimentary echolocation | Statement: [Rousettus, echolocationType, rudimentary echolocation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: echolocationType Context triple: [Rousettus, echolocationType, rudimentary echolocation]
-
A.
usesEcholocation
chosen
Indicates that an entity employs echolocation, using reflected sound waves to detect, locate, or navigate around objects or other entities.
-
B.
radarType
Indicates the specific category or classification of radar associated with an entity.
-
C.
typeOfExplorationEquipment
Indicates that one entity is a specific kind or category of exploration equipment used for investigative or exploratory activities.
-
D.
hasAcousticsSuitableFor
Indicates that something possesses acoustic properties that are appropriate or well-suited for a particular use, activity, or environment.
-
E.
radarEquipped
Indicates that an entity is equipped with or has access to radar detection equipment or radar-based sensing capability.
- 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef53930644819086b0f499e1b8ae63 |
completed | April 27, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:35 p.m.