Triple
T21067950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | And to Think That I Saw It on Mulberry Street |
E519024
|
entity |
| Predicate | hasIntendedUseContext |
P81164
|
FINISHED |
| Object | read-aloud |
—
|
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: read-aloud | Statement: [And to Think That I Saw It on Mulberry Street, hasIntendedUseContext, read-aloud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntendedUseContext Context triple: [And to Think That I Saw It on Mulberry Street, hasIntendedUseContext, read-aloud]
-
A.
hasTypicalUseContext
Indicates that something is commonly or characteristically used within a particular situation, setting, or context.
-
B.
intendedTargetContext
chosen
Indicates the context, situation, or setting that an action, message, or object is specifically designed or meant to be used in or directed toward.
-
C.
intendedWith
Indicates that one entity is the planned or desired target, recipient, or context for the use or application of another entity.
-
D.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
-
E.
containsUse
Indicates that one entity includes or makes use of another entity as part of its composition, function, or implementation.
- 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb5772481909e32af3b3a69df76 |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:45 p.m.