Triple
T11095585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kongfrontation |
E262368
|
entity |
| Predicate | simulationOf |
P31513
|
FINISHED |
| Object | encounter with King Kong |
—
|
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: encounter with King Kong | Statement: [Kongfrontation, simulationOf, encounter with King Kong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: simulationOf Context triple: [Kongfrontation, simulationOf, encounter with King Kong]
-
A.
simulationMethod
Indicates the technique or approach used to perform or implement a simulation.
-
B.
emulates
chosen
Indicates that one entity imitates or reproduces the behavior, function, or characteristics of another.
-
C.
hasSimulator
Indicates that one entity provides or is associated with a simulator used to model, emulate, or test the behavior of another entity.
-
D.
parallelExperiment
Indicates that one experiment is conducted alongside another under comparable conditions, typically for simultaneous testing or comparison.
-
E.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a0897188190b6c293b44990b3d4 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.