Triple
T7206214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phascolarctos cinereus |
E148671
|
entity |
| Predicate | sleepDurationPerDay |
P35378
|
FINISHED |
| Object | up to about 18 to 20 hours |
—
|
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 18 to 20 hours | Statement: [Phascolarctos cinereus, sleepDurationPerDay, up to about 18 to 20 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sleepDurationPerDay Context triple: [Phascolarctos cinereus, sleepDurationPerDay, up to about 18 to 20 hours]
-
A.
sleepPattern
chosen
Indicates the typical timing, duration, and regularity of an entity’s sleep over a given period.
-
B.
rotationPeriod_hours
Indicates the length of time, measured in hours, that an object takes to complete one full rotation on its axis.
-
C.
sessionLength
Indicates the duration of time that a particular session lasts from start to end.
-
D.
dosingInterval
Indicates the time period that should elapse between consecutive doses of a medication or treatment.
-
E.
settingPeriodDuration
Indicates the length of time for which a particular setting or configuration remains in effect.
- 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_69c687e8cf188190b5f3ecffd681f04e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e94ef5cc81908c33adcedf5c5054 |
completed | March 27, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69c6e757fed4819091b0a096e3befc3a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:52 p.m.