Triple
T13008927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucy’s psychiatric help booth |
E322356
|
entity |
| Predicate | hasPriceWrittenAs |
P28150
|
FINISHED |
| Object | 5¢ |
—
|
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: 5¢ | Statement: [Lucy’s psychiatric help booth, hasPriceWrittenAs, 5¢]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPriceWrittenAs Context triple: [Lucy’s psychiatric help booth, hasPriceWrittenAs, 5¢]
-
A.
isValuePriced
Indicates that something is offered at a relatively low or favorable price compared to typical or premium alternatives.
-
B.
isWritten
Indicates that a text, document, or content has been created or recorded in written form by an agent.
-
C.
hasPriceUnit
chosen
Indicates that a price value is expressed in a specific unit of currency or measurement.
-
D.
hasWrittenFor
Indicates that one entity has created written content (such as articles, stories, or texts) for or on behalf of another entity, typically a publication, organization, or platform.
-
E.
hasPriceReturnIndex
Indicates that an entity is associated with a price return index value, typically reflecting changes in price excluding income components like dividends.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e9cf0108190b02f498c6ccc91f8 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:48 p.m.