Triple
T22788052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oh Be A Fine Girl/Guy, Kiss Me |
E564026
|
entity |
| Predicate | componentForLetterF |
P149716
|
FINISHED |
| Object | Fine |
—
|
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: Fine | Statement: [Oh Be A Fine Girl/Guy, Kiss Me, componentForLetterF, Fine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentForLetterF Context triple: [Oh Be A Fine Girl/Guy, Kiss Me, componentForLetterF, Fine]
-
A.
formsFacadeOf
Indicates that one entity serves as the outward-facing surface or front (facade) of another entity, typically concealing or enclosing it.
-
B.
featuresFigureOf
Indicates that one entity includes or presents another entity as a figure, illustration, or visual element.
-
C.
featuresFictionalForm
Indicates that one entity includes, presents, or incorporates a fictional representation or version of another entity.
-
D.
componentForm
Indicates that one entity is the physical or structural component form of another, representing a part-whole or constituent relationship between them.
-
E.
characterForm
Indicates that one entity is a particular form, version, or transformation state of a character.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c32de6481909ef358d16de98496 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:29 p.m.