Triple
T6707656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lagorchestes |
E153047
|
entity |
| Predicate | typicalActivityPattern |
P51691
|
FINISHED |
| Object | nocturnal or crepuscular |
—
|
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: nocturnal or crepuscular | Statement: [Lagorchestes, typicalActivityPattern, nocturnal or crepuscular]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalActivityPattern Context triple: [Lagorchestes, typicalActivityPattern, nocturnal or crepuscular]
-
A.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
B.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
C.
typicalGoing
Indicates that an entity is engaged in or undergoing a normal, expected instance of going or movement from one place to another.
-
D.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
E.
lifeHabit
chosen
Indicates the typical way an organism lives or behaves in its environment, such as its mode of life, activity pattern, or ecological lifestyle.
- 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_69c68808d8d8819087369015270788fe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d16897e48190b43eda2206b14d6a |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d089c7488190a00853fb12f53b2a |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:06 p.m.