Triple
T18385631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parlor City |
E446581
|
entity |
| Predicate | characteristicEmphasized |
P17414
|
FINISHED |
| Object | refinement |
—
|
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: refinement | Statement: [Parlor City, characteristicEmphasized, refinement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characteristicEmphasized Context triple: [Parlor City, characteristicEmphasized, refinement]
-
A.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
B.
designEmphasizes
Indicates that a design intentionally places special importance or focus on a particular feature, principle, or aspect over others.
-
C.
valueCharacteristic
Indicates that one entity serves as a value or specific quantitative/qualitative measure that characterizes or describes another entity.
-
D.
hasEmphasis
chosen
Indicates that one element is given special stress, importance, or prominence relative to others.
-
E.
primaryCharacteristics
Indicates the main defining traits or features that most fundamentally characterize an 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e5179ecde88190b0d88c519d49e995 |
completed | April 19, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.