Triple
T31649417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fathom |
E807675
|
entity |
| Predicate | hasPlannedAdaptationType |
P117916
|
FINISHED |
| Object | live-action film |
—
|
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: live-action film | Statement: [Fathom, hasPlannedAdaptationType, live-action film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedAdaptationType Context triple: [Fathom, hasPlannedAdaptationType, live-action film]
-
A.
plannedAdaptation
Indicates that an adaptation or modification has been intentionally designed or scheduled to occur in response to certain conditions or goals.
-
B.
adaptationPlannedAs
Indicates that a specific adaptation or modification is scheduled or intended to be carried out in relation to another entity.
-
C.
adaptationType
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
D.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
-
E.
hasWorkAdaptationType
chosen
Indicates the type of adaptation or modification applied to a work (e.g., translation, abridgment, dramatization) in relation to its original form.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 30, 2026, 10:52 p.m.