Triple
T3834397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rod Nam Dam Hua |
E91093
|
entity |
| Predicate | typicalDateRange |
P18044
|
FINISHED |
| Object | 13–15 April |
—
|
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: 13–15 April | Statement: [Rod Nam Dam Hua, typicalDateRange, 13–15 April]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDateRange Context triple: [Rod Nam Dam Hua, typicalDateRange, 13–15 April]
-
A.
typicalDates
chosen
Indicates the usual or standard dates during which something typically occurs, is valid, or is scheduled.
-
B.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
C.
collectionTimespan
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
D.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
E.
representsDateRange
Indicates that a subject is associated with, valid for, or applicable during a specific start-to-end date range.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8a27688190866bc41441e2260c |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.