Triple
T34316514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebastes rubrivinctus |
E880598
|
entity |
| Predicate | dayActivity |
P10350
|
FINISHED |
| Object | often found near the bottom during the day |
—
|
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: often found near the bottom during the day | Statement: [Sebastes rubrivinctus, dayActivity, often found near the bottom during the day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dayActivity Context triple: [Sebastes rubrivinctus, dayActivity, often found near the bottom during the day]
-
A.
hasDayActivity
Indicates that an entity engages in or is associated with a specific activity that occurs during the daytime.
-
B.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
C.
activityFocus
Indicates that an activity is primarily directed toward, centered on, or concerned with a particular object, topic, or goal.
-
D.
activityTime
chosen
Indicates the time period during which an activity occurs or is scheduled to take place.
-
E.
activitiesCarriedOutFor
Indicates that certain activities are performed on behalf of, in service of, or for the benefit of a particular entity.
- 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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.