Triple
T25149082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairy Tales Told for Children |
E630018
|
entity |
| Predicate | hasEarlyVersionOf |
P60231
|
FINISHED |
| Object | The Little Mermaid |
—
|
NE NERFINISHED |
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: The Little Mermaid | Statement: [Fairy Tales Told for Children, hasEarlyVersionOf, The Little Mermaid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarlyVersionOf Context triple: [Fairy Tales Told for Children, hasEarlyVersionOf, The Little Mermaid]
-
A.
hasEarlierVersion
chosen
Indicates that one entity is an earlier or prior version of another entity in a version sequence.
-
B.
earlierVersionsCapability
Indicates that an entity has the ability to access, handle, or interact with earlier versions of another entity or resource.
-
C.
isYoungerVersionOf
Indicates that one entity represents the same individual as another entity, but at an earlier, younger stage in their life.
-
D.
hasSmallerVersion
Indicates that one entity exists as a reduced-size or smaller-scale version of another entity.
-
E.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4684f11708190aa73600e3367475b |
completed | May 1, 2026, 8:46 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:30 a.m.