Triple
T6966354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Movin' On Up |
E161497
|
entity |
| Predicate | oftenUsedToSymbolize |
P18980
|
FINISHED |
| Object | moving to a better neighborhood |
—
|
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: moving to a better neighborhood | Statement: [Movin' On Up, oftenUsedToSymbolize, moving to a better neighborhood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenUsedToSymbolize Context triple: [Movin' On Up, oftenUsedToSymbolize, moving to a better neighborhood]
-
A.
symbolizes
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
B.
oftenUsedAsNameFor
Indicates that something frequently serves as a name or designation for another entity.
-
C.
typicalSymbol
chosen
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
-
D.
symbolicallyUses
Indicates that one entity employs another as a symbol or representation to convey meaning, ideas, or associations rather than for its literal or practical function.
-
E.
oftenUsedAfter
Indicates that one entity is frequently or typically used immediately following another entity in a sequence or workflow.
- 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db121174819098e73e45f6c9cc91 |
completed | March 27, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.