Triple
T16069323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Kong vs. Godzilla |
E389816
|
entity |
| Predicate | hasDifferentCut |
P57506
|
FINISHED |
| Object | American re-edited version |
—
|
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: American re-edited version | Statement: [King Kong vs. Godzilla, hasDifferentCut, American re-edited version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDifferentCut Context triple: [King Kong vs. Godzilla, hasDifferentCut, American re-edited version]
-
A.
hasCut
Indicates that one entity has made or possesses a cut in, on, or through another entity.
-
B.
hasAlternateCut
chosen
Indicates that an entity has an alternative edited version or cut, distinct from its primary or original form.
-
C.
hasTypicalCut
Indicates that one entity is characterized by or associated with a standard or typical type of cut of another entity.
-
D.
isCutInto
Indicates that one entity is divided or separated into pieces or segments that become the other entity.
-
E.
hasCutAfterRound
Indicates that an entity is eliminated or removed from participation after a specified round.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.