Triple
T15965464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stupid with Love |
E387177
|
entity |
| Predicate | plotPosition |
P98770
|
FINISHED |
| Object | early in the musical |
—
|
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: early in the musical | Statement: [Stupid with Love, plotPosition, early in the musical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plotPosition Context triple: [Stupid with Love, plotPosition, early in the musical]
-
A.
playingPosition
Indicates the specific role or position an individual occupies while participating in a game or sport.
-
B.
chartPosition
Indicates the ranking or placement of an item within an ordered chart or list at a specific point in time.
-
C.
parallelPosition
Indicates that two entities occupy positions that are aligned in parallel relative to a reference frame or axis.
-
D.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
E.
positionInAct
chosen
Indicates the specific location or role that something occupies within a particular act or segment of a larger sequence or performance.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.