Triple
T38545333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariel (mute version) |
E924948
|
entity |
| Predicate | keyPlotElementIn |
P95467
|
FINISHED |
| Object | romantic storyline with Prince Eric |
—
|
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: romantic storyline with Prince Eric | Statement: [Ariel (mute version), keyPlotElementIn, romantic storyline with Prince Eric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyPlotElementIn Context triple: [Ariel (mute version), keyPlotElementIn, romantic storyline with Prince Eric]
-
A.
isKeyToPlotOf
chosen
Indicates that something plays a crucial, defining role in driving or enabling the main events or structure of a plot.
-
B.
keyOf
Indicates that one entity functions as the key (identifier or access token) associated with another entity.
-
C.
keyLine
Indicates that a line or segment serves as a primary or defining reference line within a structure, system, or representation.
-
D.
keyThemeIn
Indicates that a particular theme is a central or primary thematic focus within a given work, context, or subject.
-
E.
keyRuleDepicted
Indicates that a visual representation depicts or illustrates a key rule or governing principle relevant to the associated entities.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd2ee29a081908309dba59b18686a |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f81cbc8190b4fd3bfc3106c1f3 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.