Triple
T28782786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Denisovich Shukhov |
E726718
|
entity |
| Predicate | dailyActivityInCamp |
P1164
|
FINISHED |
| Object | construction work |
—
|
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: construction work | Statement: [Ivan Denisovich Shukhov, dailyActivityInCamp, construction work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dailyActivityInCamp Context triple: [Ivan Denisovich Shukhov, dailyActivityInCamp, construction work]
-
A.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
B.
typicalActivity
chosen
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
C.
day1Event
Indicates that an event occurs on or is associated with the first day of a specified period or sequence.
-
D.
servesCamp
Indicates that an entity provides services, support, or functions in a role dedicated to a particular camp or camp-related organization.
-
E.
hasHumanActivities
Indicates that certain human actions, behaviors, or practices are present, performed, or associated with a given 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:20 a.m.