Triple
T36718470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goldilocks |
E906979
|
entity |
| Predicate | famousLineTheme |
P187100
|
FINISHED |
| Object | just right |
—
|
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: just right | Statement: [Goldilocks, famousLineTheme, just right]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousLineTheme Context triple: [Goldilocks, famousLineTheme, just right]
-
A.
famousLineSpeaker
Indicates that the subject is the person who spoke or delivered the famous line referenced by the object.
-
B.
famousLineSourceOde
Indicates that one entity is the source or origin of a famous line found in the ode represented by the other entity.
-
C.
usedCatchphraseTheme
Indicates that an entity employed a particular catchphrase as a recurring thematic element or motif.
-
D.
famousCall
Indicates that one entity makes a phone call to another entity who is widely known or celebrated.
-
E.
famousTry
Indicates an attempt or effort that is widely recognized or notable, often because it is well-known, celebrated, or frequently referenced.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: May 3, 2026, 4:12 p.m.