Triple
T8043762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Bigger Splash |
E187497
|
entity |
| Predicate | hasNoVisibleHumanFigures |
P33022
|
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: [A Bigger Splash, hasNoVisibleHumanFigures, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoVisibleHumanFigures Context triple: [A Bigger Splash, hasNoVisibleHumanFigures, true]
-
A.
containsHumanFigures
Indicates that the subject includes one or more human figures within its content or composition.
-
B.
hasNoDepictionOf
chosen
Indicates that the subject lacks any visual or graphical representation of the specified object or concept.
-
C.
includesNonHumanCharacters
Indicates that the subject contains or features characters that are not human, such as animals, aliens, or other non-human entities.
-
D.
doesNotFeatureCharacterDirectly
Indicates that the subject work does not include the specified character as an on-screen, on-page, or otherwise directly appearing participant in its content.
-
E.
isHuman
Indicates that the subject entity possesses the defining characteristics or status of being a human.
- 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f4b5e0c819092949af0f995b850 |
completed | March 31, 2026, 3:28 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:23 p.m.