Triple
T32458192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jianyuan |
E829487
|
entity |
| Predicate | startDate_calendar |
P288
|
FINISHED |
| Object | 140 BC (Liu Che’s accession era) |
—
|
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: 140 BC (Liu Che’s accession era) | Statement: [Jianyuan, startDate_calendar, 140 BC (Liu Che’s accession era)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startDate_calendar Context triple: [Jianyuan, startDate_calendar, 140 BC (Liu Che’s accession era)]
-
A.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
-
B.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
C.
dateOfEventCommand
Indicates a command or instruction that specifies or requests the date on which an event occurs.
-
D.
startDateInMonth
Indicates that an entity’s start date falls within a specified calendar month.
-
E.
eventDateContext
Indicates the contextual role or significance that a specific date has within an event (e.g., whether it is the start, end, deadline, or another relevant temporal marker).
- 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_69f3491df9288190afc0b23b1d6e72ce |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: May 1, 2026, 12:56 a.m.