Triple
T27114096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oh My General |
E686792
|
entity |
| Predicate | hasRomanticPairing |
P143936
|
FINISHED |
| Object | Ye Zhao and Zhao Yujin |
—
|
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: Ye Zhao and Zhao Yujin | Statement: [Oh My General, hasRomanticPairing, Ye Zhao and Zhao Yujin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanticPairing Context triple: [Oh My General, hasRomanticPairing, Ye Zhao and Zhao Yujin]
-
A.
hasRomanticPlotline
Indicates that there is a romantic storyline or relationship development present between the entities.
-
B.
hasRomanticSubplot
Indicates that a work includes a secondary storyline centered on a romantic relationship between characters.
-
C.
hasRomanticMisadventures
Indicates that an entity experiences a series of problematic, comical, or unsuccessful romantic relationships or encounters.
-
D.
canRomanceMultipleCharacters
Indicates that an entity is able to pursue romantic relationships with more than one character.
-
E.
romanticPartnerInSeries
chosen
Indicates that one character is portrayed as a romantic partner of another character within the context of a specific series or narrative.
- 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 27, 2026, 8:55 a.m.