Triple
T28075780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longzhong Plan |
E709537
|
entity |
| Predicate | laterInterpretedIn |
P34632
|
FINISHED |
| Object | Romance of the Three Kingdoms |
—
|
NE NERFINISHED |
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: Romance of the Three Kingdoms | Statement: [Longzhong Plan, laterInterpretedIn, Romance of the Three Kingdoms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterInterpretedIn Context triple: [Longzhong Plan, laterInterpretedIn, Romance of the Three Kingdoms]
-
A.
laterReinterpretedAs
chosen
Indicates that something was originally understood or classified one way but was subsequently given a different interpretation or meaning at a later time.
-
B.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
C.
laterExtendedIn
Indicates that an existing entity (such as a work, version, or specification) was subsequently expanded, updated, or built upon by a later entity.
-
D.
laterDeployedIn
Indicates that one entity was deployed or put into operation in a particular context, location, or system at a later time than another.
-
E.
laterWithin
Indicates that one event or time point occurs later than another while still falling within a specified temporal interval or boundary.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 27, 2026, 8:48 p.m.