Triple
T19714379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Kong (video game, 1982) |
E473433
|
entity |
| Predicate | isLooselyAdaptedFrom |
P1245
|
FINISHED |
| Object | classic King Kong 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: classic King Kong film | Statement: [King Kong (video game, 1982), isLooselyAdaptedFrom, classic King Kong film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLooselyAdaptedFrom Context triple: [King Kong (video game, 1982), isLooselyAdaptedFrom, classic King Kong film]
-
A.
inspiredByAdaptationOf
Indicates that something draws its inspiration from an adaptation (rather than the original source) of another work or entity.
-
B.
hasHumanAdaptation
Indicates that something has been modified, designed, or adjusted specifically to suit human use, abilities, or needs.
-
C.
developedFrom
chosen
Indicates that one entity originates, evolves, or is derived from another as its source or precursor.
-
D.
adoptedFrom
Indicates that an entity has been taken into guardianship, ownership, or use from another source or origin.
-
E.
adaptationOrigin
Indicates the source or basis from which an adaptation is derived or developed.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6440b47508190a8a33325b00841dc |
completed | April 20, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.