Triple
T37151893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Han Seoul-Oh |
E920382
|
entity |
| Predicate | revealedAliveIn |
P38401
|
FINISHED |
| Object | F9 |
—
|
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: F9 | Statement: [Han Seoul-Oh, revealedAliveIn, F9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revealedAliveIn Context triple: [Han Seoul-Oh, revealedAliveIn, F9]
-
A.
isRevealedIn
chosen
Indicates that something becomes known, disclosed, or made apparent within a particular context, medium, or situation.
-
B.
appearsInRevival
Indicates that an entity participates in, is featured in, or is otherwise present within a revival or revived version of another work, event, or production.
-
C.
isAliveInCanon
Indicates that the subject character is currently alive within the official storyline or continuity of the work.
-
D.
isSurvivorOf
Indicates that one entity has lived through, endured, or remained alive after a particular event, condition, or harmful circumstance involving another entity.
-
E.
revealedAfter
Indicates that one piece of information, event, or state becomes known or disclosed only subsequent to another specified point in time or condition.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.