Triple
T27688717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liu Rong |
E698100
|
entity |
| Predicate | positionStartContext |
P184588
|
FINISHED |
| Object | early reign of Emperor Jing of Han |
—
|
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: early reign of Emperor Jing of Han | Statement: [Liu Rong, positionStartContext, early reign of Emperor Jing of Han]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionStartContext Context triple: [Liu Rong, positionStartContext, early reign of Emperor Jing of Han]
-
A.
positionStartFor
Indicates the starting position or initial point at which an entity, event, or interval begins relative to another reference.
-
B.
holderPositionStart
Indicates the starting spatial position or location of the holder in relation to another entity or context.
-
C.
positionStartTime
Indicates the time at which a position, role, or placement begins.
-
D.
positionBefore
Indicates that one entity occurs or is arranged earlier in order or sequence than another entity.
-
E.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
- F. None of above. chosen
Provenance (4 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: April 27, 2026, 2:50 p.m.