Triple
T23731482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HYBE Corporation |
E586419
|
entity |
| Predicate | managesAct |
P104809
|
FINISHED |
| Object | BTS |
—
|
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: BTS | Statement: [HYBE Corporation, managesAct, BTS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesAct Context triple: [HYBE Corporation, managesAct, BTS]
-
A.
managedAct
Indicates that one entity oversaw, directed, or was responsible for carrying out a particular action or activity.
-
B.
managingFor
Indicates that one entity is responsible for directing, supervising, or overseeing activities, resources, or operations on behalf of another entity.
-
C.
managementIs
chosen
Indicates that one entity holds a managerial role, responsibility, or authority over another entity.
-
D.
manageThrough
Indicates that one entity exercises control, direction, or administration over another entity or process by means of an intermediary entity, channel, or mechanism.
-
E.
managedAffairsOf
Indicates that one entity was responsible for handling, overseeing, or conducting the business, administrative, or personal matters of 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b9193b14819096f1c7b11a441569 |
completed | April 29, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:09 p.m.