Triple
T17962450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian crested porcupine |
E449115
|
entity |
| Predicate | restPeriod |
P123821
|
FINISHED |
| Object | daytime |
—
|
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: daytime | Statement: [Indian crested porcupine, restPeriod, daytime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restPeriod Context triple: [Indian crested porcupine, restPeriod, daytime]
-
A.
restDays
Indicates the number or specific days allocated for rest or non-working periods in relation to an entity or schedule.
-
B.
dormancyPeriod
Indicates the length of time an entity remains inactive or in a dormant state before resuming activity.
-
C.
shutdownPeriod
Indicates a time interval during which a system, service, or process is intentionally turned off or not operational.
-
D.
restingBehavior
chosen
Indicates a relationship where an entity is in a state of rest or inactivity, typically pausing movement or action for recovery or idling.
-
E.
cooldown
Indicates that an entity must wait a specified period of time before performing the same action or a related action again.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b134bc68819097cc199ea8e80f6c |
completed | April 19, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.