Triple
T19513381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarence Mill |
E488211
|
entity |
| Predicate | hasConversion |
P631
|
FINISHED |
| Object | mixed-use development |
—
|
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: mixed-use development | Statement: [Clarence Mill, hasConversion, mixed-use development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConversion Context triple: [Clarence Mill, hasConversion, mixed-use development]
-
A.
allowsConversionTo
Indicates that one entity permits or enables transformation or change into another specified form or state.
-
B.
hasConversionIssueWith
Indicates that one entity experiences or is associated with a problem, error, or incompatibility when being converted to or from another entity.
-
C.
involvesConversionFrom
Indicates that one entity participates in or requires a transformation or change from another entity as its source or starting point.
-
D.
convertsTo
chosen
Indicates that one entity is transformed or changed into another entity, typically resulting in a different state, form, or representation.
-
E.
methodOfConversion
Indicates the specific process or technique used to transform one form, state, or representation into another.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63599c17881909a392a6026e45955 |
completed | April 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.