Triple
T11843848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caribbean spiny lobster |
E281721
|
entity |
| Predicate | nighttimeBehavior |
P26548
|
FINISHED |
| Object | forages on the seafloor |
—
|
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: forages on the seafloor | Statement: [Caribbean spiny lobster, nighttimeBehavior, forages on the seafloor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nighttimeBehavior Context triple: [Caribbean spiny lobster, nighttimeBehavior, forages on the seafloor]
-
A.
isNocturnal
Indicates that an entity is primarily active during the night and rests during the day.
-
B.
nightService
Indicates that a service operates or is available during nighttime hours.
-
C.
nightServicePattern
Indicates that a service or operation follows a specific pattern or schedule that applies only during nighttime hours.
-
D.
nightActivityLevel
Indicates the intensity or extent of an entity’s actions or behavior occurring during nighttime hours.
-
E.
associatedNightTiming
chosen
Indicates a relationship where an event, action, or condition is linked specifically to a time period occurring during the night.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65a597c8190b09f57463b279afc |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.