Triple
T6051898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hop (2011 film) |
E134813
|
entity |
| Predicate | usesLiveAction |
P35284
|
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: [Hop (2011 film), usesLiveAction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLiveAction Context triple: [Hop (2011 film), usesLiveAction, true]
-
A.
containsLiveAction
chosen
Indicates that something includes or features live-action content, typically involving real-world footage or live actors rather than solely animation or static media.
-
B.
liveAction
Indicates that an entity is a live-action (non-animated) adaptation, portrayal, or version of another entity.
-
C.
hasLiveBroadcast
Indicates that a live broadcast is currently being transmitted or available for the referenced entity.
-
D.
hasLiveActionVersion
Indicates that an entity has a corresponding adaptation or version produced in live-action (with real actors and physical settings) rather than animation or other non-live formats.
-
E.
hasAct
Indicates that an entity performs, participates in, or is associated with a specific act or action.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056f802988190aafdb7cbb087c828 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:09 p.m.