Triple
T10606375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | striped hyena |
E275885
|
entity |
| Predicate | maneFunction |
P94890
|
FINISHED |
| Object | raised when threatened to appear larger |
—
|
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: raised when threatened to appear larger | Statement: [striped hyena, maneFunction, raised when threatened to appear larger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maneFunction Context triple: [striped hyena, maneFunction, raised when threatened to appear larger]
-
A.
metaFunction
Indicates that one function operates on, describes, or manipulates other functions or their behavior at a higher (meta) level.
-
B.
mainFunctions
Indicates that the subject serves as the primary or central functional component or role for the object.
-
C.
functie
Indicates that one entity serves as a function, role, or operational purpose in relation to another entity.
-
D.
deFactoFunction
Indicates that one entity effectively serves or operates in the role or capacity of another entity, even if not formally or officially designated as such.
-
E.
hadFunction
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df4b7aa48190bf7873b293571030 |
completed | April 8, 2026, 11:05 p.m. |
| PD | Predicate disambiguation | batch_69d6dd72c1288190adbb5e79e94c044a |
completed | April 8, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 7:32 p.m.