Triple
T17311858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Crack in the Wall |
E420318
|
entity |
| Predicate | recursAs |
P126929
|
FINISHED |
| Object | central plot element |
—
|
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: central plot element | Statement: [The Crack in the Wall, recursAs, central plot element]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recursAs Context triple: [The Crack in the Wall, recursAs, central plot element]
-
A.
recursIn
Indicates that an event, pattern, or entity appears repeatedly or returns multiple times within a given context, sequence, or timeframe.
-
B.
recurs
Indicates that an event, condition, or pattern happens again, often repeatedly or at regular intervals, after having occurred before.
-
C.
usesRecursion
Indicates that an entity performs an operation or defines a process by invoking itself, directly or indirectly, as part of its execution.
-
D.
recastBy
Indicates that an existing role, character, or part has been newly assigned to a different performer or entity than before.
-
E.
recastOf
Indicates that one entity is a new or different version, adaptation, or reinterpretation of another, typically replacing or redoing the original in a similar role or context.
- F. None of above. chosen
Provenance (4 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439993bac8190a72f6af529bd7cce |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:43 a.m.