Triple
T18588260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Que Sera, Sera (Whatever Will Be, Will Be) |
E454293
|
entity |
| Predicate | questionsAddressedByChild |
P97881
|
FINISHED |
| Object | What will I be? |
—
|
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: What will I be? | Statement: [Que Sera, Sera (Whatever Will Be, Will Be), questionsAddressedByChild, What will I be?]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questionsAddressedByChild Context triple: [Que Sera, Sera (Whatever Will Be, Will Be), questionsAddressedByChild, What will I be?]
-
A.
questionConveyedBy
Indicates that a particular question is expressed, communicated, or represented by a given medium, message, or artifact.
-
B.
asksChildrenTo
Indicates that one entity requests or directs children to perform an action or respond in some way.
-
C.
daughterRequest
Indicates that a daughter is making a request to someone, typically seeking permission, help, or a desired action.
-
D.
typicalQuestion
chosen
Indicates that an entity is a common or standard question typically asked in a given context or situation.
-
E.
canAnswerQuestions
Indicates that an entity has the ability or capacity to respond correctly or appropriately to questions.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b3e564819088e60fc25d1976f0 |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.