Triple
T34645353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tae Young |
E889678
|
entity |
| Predicate | hasFandomRole |
P191982
|
FINISHED |
| Object | heartthrob member of 4*Town |
—
|
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: heartthrob member of 4*Town | Statement: [Tae Young, hasFandomRole, heartthrob member of 4*Town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFandomRole Context triple: [Tae Young, hasFandomRole, heartthrob member of 4*Town]
-
A.
hasFandomAssociation
chosen
Indicates a relationship where an entity is associated with, connected to, or recognized within a particular fandom or fan community.
-
B.
hasFandomElement
Indicates that something includes, features, or is associated with an element derived from or related to a fandom.
-
C.
hasFandomDesignation
Indicates that an entity has a specific name or label used by its fan community to refer to it or its fandom.
-
D.
hasBelovedRole
Indicates that an entity holds a role or position that is deeply cherished or loved by another entity.
-
E.
hasInUniverseRole
Indicates that an entity holds or performs a specific role or function within a particular fictional or defined universe.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 1, 2026, 2:04 a.m.