Triple
T1104482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hallyu |
E25455
|
entity |
| Predicate | mainDomain |
P1902
|
FINISHED |
| Object | popular culture |
—
|
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: popular culture | Statement: [Hallyu, mainDomain, popular culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainDomain Context triple: [Hallyu, mainDomain, popular culture]
-
A.
primaryDomain
chosen
Indicates that one domain is the main or most important domain associated with an entity, as opposed to any secondary or alternate domains.
-
B.
standardDomain
Indicates that something belongs to, or is defined within, the usual or default domain of discourse or applicability for a given context.
-
C.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
-
D.
secondaryDomain
Indicates that one domain functions as a secondary or auxiliary domain in relation to a primary domain.
-
E.
mainBase
Indicates that one entity serves as the primary or central base or headquarters for another entity.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9e1047481909af1cf8df2a01fff |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b7472c848190b0643872f67084a2 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.