Triple
T28433594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oath of the Peach Garden |
E715202
|
entity |
| Predicate | involvesVow |
P23834
|
FINISHED |
| Object | to live and die together as brothers |
—
|
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: to live and die together as brothers | Statement: [Oath of the Peach Garden, involvesVow, to live and die together as brothers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesVow Context triple: [Oath of the Peach Garden, involvesVow, to live and die together as brothers]
-
A.
hasVow
chosen
Indicates that one entity has made or is bound by a formal vow or promise in relation to another entity or context.
-
B.
vowStatus
Indicates the current state or condition of a commitment or promise made between entities, such as whether it is active, fulfilled, or broken.
-
C.
associatedVow
Indicates a relationship where a vow is linked or connected to a particular entity or event.
-
D.
vowResult
Indicates that a vow or solemn promise leads to, results in, or is fulfilled by a particular outcome or state.
-
E.
vowPractice
Indicates that an entity engages in or upholds a particular vow, promise, or solemn commitment as an ongoing practice.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 1:41 a.m.