Triple
T22788042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oh Be A Fine Girl/Guy, Kiss Me |
E564026
|
entity |
| Predicate | hasFirstLetterSequence |
P27166
|
FINISHED |
| Object | O B A F G K M |
—
|
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: O B A F G K M | Statement: [Oh Be A Fine Girl/Guy, Kiss Me, hasFirstLetterSequence, O B A F G K M]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstLetterSequence Context triple: [Oh Be A Fine Girl/Guy, Kiss Me, hasFirstLetterSequence, O B A F G K M]
-
A.
hasInitialLetters
chosen
Indicates that one entity’s initial letters or acronym are derived from or correspond to the other entity.
-
B.
letterSequence
Indicates that one sequence of letters directly follows or is ordered in relation to another within a larger string or alphabetic arrangement.
-
C.
hasLetter
Indicates that one entity contains, includes, or is associated with a specific letter or character.
-
D.
eachStanzaBeginsWithLetterOf
Indicates that every stanza in a text starts with a specific given letter.
-
E.
hasLetterPattern
Indicates that one entity exhibits or matches a specific sequence or arrangement of letters defined by 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_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. |
Created at: April 17, 2026, 3:29 p.m.