Triple
T23900319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lion |
E601022
|
entity |
| Predicate | roarAudibility |
P45475
|
FINISHED |
| Object | up to about 8 km |
—
|
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: up to about 8 km | Statement: [Lion, roarAudibility, up to about 8 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roarAudibility Context triple: [Lion, roarAudibility, up to about 8 km]
-
A.
hasAcousticsSuitableFor
Indicates that something possesses acoustic properties that are appropriate or well-suited for a particular use, activity, or environment.
-
B.
audibleIn
chosen
Indicates that a sound produced by one entity can be heard within the spatial or contextual range of another entity.
-
C.
hearingAbility
Indicates the capacity or level to which an entity can perceive and interpret sound through hearing.
-
D.
canRoar
Indicates that one entity has the ability to produce a roar, typically a loud, deep vocalization.
-
E.
canHear
Indicates that one entity is able to perceive sounds produced by 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cdddca088190b6c26df984a143ad |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:26 p.m.