Triple
T5788666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Matcham |
E128335
|
entity |
| Predicate | designedApproximately |
P65843
|
FINISHED |
| Object | over 80 theatres |
—
|
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: over 80 theatres | Statement: [Frank Matcham, designedApproximately, over 80 theatres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedApproximately Context triple: [Frank Matcham, designedApproximately, over 80 theatres]
-
A.
approximateDesignYear
Indicates the estimated or inferred year in which something was designed, rather than a precisely known design year.
-
B.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
C.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
D.
hasDimensionsApprox
Indicates that an entity has physical dimensions that are known only approximately, rather than as exact measurements.
-
E.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
- F. None of above. chosen
Provenance (4 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a53d0148190bdebc4f5609939ac |
completed | March 22, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c024861bc88190a17782c1982fbb3e |
completed | March 22, 2026, 5:19 p.m. |
Created at: March 22, 2026, 3:51 p.m.