Triple
T1453557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snap the Whip |
E31346
|
entity |
| Predicate | hasBackgroundElement |
P26195
|
FINISHED |
| Object | one-room schoolhouse |
—
|
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: one-room schoolhouse | Statement: [Snap the Whip, hasBackgroundElement, one-room schoolhouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBackgroundElement Context triple: [Snap the Whip, hasBackgroundElement, one-room schoolhouse]
-
A.
hasBackground
Indicates that an entity possesses or is associated with a particular background, such as context, setting, or prior circumstances.
-
B.
hasSuperstrate
Indicates that one material, layer, or structure lies above and is supported by another in a layered or composite arrangement.
-
C.
hasFront
Indicates that an entity possesses or is associated with a front-facing side, surface, or portion.
-
D.
formsBackdropOf
chosen
Indicates that one entity serves as the background or setting against which another entity is viewed, occurs, or is presented.
-
E.
hasBlock
Indicates that one entity possesses, contains, or is associated with a specific block or blocking element in relation to another entity.
- 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c57e82d48190a30a4512f39f5de0 |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47cdbd0819092022344a2f4ad7b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.