Triple
T5691087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korean film industry |
E125428
|
entity |
| Predicate | beganToGlobalize |
P65980
|
FINISHED |
| Object | late 1990s |
—
|
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: late 1990s | Statement: [Korean film industry, beganToGlobalize, late 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganToGlobalize Context triple: [Korean film industry, beganToGlobalize, late 1990s]
-
A.
hasGlobalRegion
Indicates that an entity is associated with or belongs to a specific global geographic region.
-
B.
hasGlobalReach
Indicates that an entity’s influence, operations, or impact extends across multiple countries or worldwide.
-
C.
globalVersion
Indicates that one entity represents a version or variant that is globally applicable or recognized for another entity.
-
D.
useBegan
Indicates that an entity initiated or started using another entity or resource at a particular point in time.
-
E.
uniformizedBy
Indicates that one entity has been made uniform, standardized, or brought into a consistent form or structure by another entity.
- F. None of above. chosen
Provenance (4 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c0e0408190ab6c3cd3f907e80f |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c028fec2bc819083f5dca6a8d9d435 |
completed | March 22, 2026, 5:38 p.m. |
Created at: March 22, 2026, 3:44 p.m.