Triple
T28831582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ptilocercidae |
E728063
|
entity |
| Predicate | temporalActivityPattern |
P77564
|
FINISHED |
| Object | nocturnal |
—
|
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: nocturnal | Statement: [Ptilocercidae, temporalActivityPattern, nocturnal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalActivityPattern Context triple: [Ptilocercidae, temporalActivityPattern, nocturnal]
-
A.
travelPattern
Indicates the typical routes, frequencies, and behaviors associated with how an entity moves or travels between locations.
-
B.
hasFootfallPattern
Indicates a characteristic pattern or sequence of steps, movements, or impacts made by an entity’s feet during locomotion or activity.
-
C.
someSpeciesActivityPattern
chosen
Indicates that a species exhibits a particular temporal pattern of activity (e.g., diurnal, nocturnal, crepuscular) in its daily or seasonal behavior.
-
D.
primaryActivityPattern
Indicates the main recurring type of activity or behavior that characterizes how an entity typically operates or functions.
-
E.
typicalStayPattern
Indicates the usual or characteristic way in which an entity remains or stays in a place or state over time.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6593ca620819080169328db2e16e9 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:37 a.m.