Triple
T34364364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feel Special |
E881966
|
entity |
| Predicate | subUnitRapBy |
P179133
|
FINISHED |
| Object | Dahyun |
—
|
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: Dahyun | Statement: [Feel Special, subUnitRapBy, Dahyun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subUnitRapBy Context triple: [Feel Special, subUnitRapBy, Dahyun]
-
A.
subunitRatio
Indicates the proportional relationship between the quantities or sizes of different subunits within a larger whole.
-
B.
subunitType
Indicates that one entity is a specific kind or classification of subunit within the structure or composition of another entity.
-
C.
subunitOf
Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
-
D.
registrationUnit
Indicates that one entity serves as the official unit or body responsible for registering, recording, or enrolling another entity.
-
E.
subunitNameSingular
Indicates that the predicate specifies the singular form of the name for a subunit within a larger entity or structure.
- 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71c33edac8190a59f6ff19b265fc5 |
completed | May 3, 2026, 9:58 a.m. |
Created at: May 1, 2026, 1:58 a.m.