Triple
T29320071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Velli |
E743491
|
entity |
| Predicate | typicalWorkPattern |
P36842
|
FINISHED |
| Object | regular working day in modern Tamil-speaking societies |
—
|
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: regular working day in modern Tamil-speaking societies | Statement: [Velli, typicalWorkPattern, regular working day in modern Tamil-speaking societies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWorkPattern Context triple: [Velli, typicalWorkPattern, regular working day in modern Tamil-speaking societies]
-
A.
workPattern
chosen
Indicates the typical schedule, structure, or arrangement according to which an entity performs its work or duties.
-
B.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
C.
typicalShift
Indicates that the specified time period represents the usual or standard work shift associated with an entity.
-
D.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
E.
timePeriodOfWorks
Indicates the span of time during which the associated works were created, produced, or active.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a01a0b63d148190b10206509c0a0a5b |
completed | May 11, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_6a01a0245d4c8190a3c3fbbe83f0389d |
completed | May 11, 2026, 9:23 a.m. |
Created at: April 28, 2026, 1:22 p.m.