Triple
T34500115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Lord Fauntleroy (1980 television film) |
E885726
|
entity |
| Predicate | isAdaptationOfClassic |
P43664
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Little Lord Fauntleroy (1980 television film), isAdaptationOfClassic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAdaptationOfClassic Context triple: [Little Lord Fauntleroy (1980 television film), isAdaptationOfClassic, true]
-
A.
isAdaptation
chosen
Indicates that one work is derived from, based on, or reinterprets the content of another work.
-
B.
consideredClassic
Indicates that something is widely regarded or recognized as a classic within a particular field, genre, or context.
-
C.
isClassicWinner
Indicates that an entity has won a classic or traditionally recognized competition, award, or title.
-
D.
isClassicOfArea
Indicates that something is recognized as a classic or exemplary work within a particular area, field, or domain.
-
E.
isClassicNumber
Indicates that a number belongs to a traditionally recognized or canonical set of numbers defined as "classic" within a given context.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:01 a.m.