Triple
T19856649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francis-Jones Morehen Thorp |
E477148
|
entity |
| Predicate | design approach |
P532
|
FINISHED |
| Object | public realm-focused design |
—
|
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: public realm-focused design | Statement: [Francis-Jones Morehen Thorp, design approach, public realm-focused design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: design approach Context triple: [Francis-Jones Morehen Thorp, design approach, public realm-focused design]
-
A.
documentsDesignApproachOf
Indicates that one entity records or specifies the design approach used for another entity.
-
B.
designMethod
Indicates that one entity is used as the method, approach, or technique by which another entity is designed or created.
-
C.
designAspect
Indicates that one entity represents a particular design-related feature, characteristic, or consideration of another entity.
-
D.
designProcess
Indicates the sequence of actions, decisions, and iterations involved in creating, developing, or refining a design.
-
E.
designPhilosophy
chosen
Indicates the guiding principles, values, or conceptual approach that shape how something is designed or created.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6586cd8f08190b34c8886e8617255 |
completed | April 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.