Triple
T298427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sciuridae |
E6143
|
entity |
| Predicate | typicalBehavior |
P1164
|
FINISHED |
| Object | diurnal in many species |
—
|
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: diurnal in many species | Statement: [Sciuridae, typicalBehavior, diurnal in many species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBehavior Context triple: [Sciuridae, typicalBehavior, diurnal in many species]
-
A.
behaviorNear
Indicates that one entity exhibits a behavior or action in close spatial proximity to another entity.
-
B.
typicalAssumption
Indicates that something is taken as a standard or default assumption that generally holds in typical or normal circumstances.
-
C.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
D.
typicalEvent
Indicates that the associated event is a common, characteristic, or prototypical occurrence for the given entity or situation.
-
E.
typicalActivity
chosen
Indicates that an entity is commonly or characteristically engaged in a particular activity.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea4778cc8190be7b648a82542891 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e937af888190a0960708f09ae033 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.