Triple
T19856641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francis-Jones Morehen Thorp |
E477148
|
entity |
| Predicate | has notable work type |
P126210
|
FINISHED |
| Object | public buildings |
—
|
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 buildings | Statement: [Francis-Jones Morehen Thorp, has notable work type, public buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has notable work type Context triple: [Francis-Jones Morehen Thorp, has notable work type, public buildings]
-
A.
workTypeContributedTo
Indicates that an entity contributed to the creation, development, or production of a particular type of work.
-
B.
hasSignificantWorkType
chosen
Indicates that an entity is associated with a primary or notably important type or category of work.
-
C.
notableWorkPerformed
Indicates that an entity has created, executed, or contributed significantly to a particular work that is recognized as notable or important.
-
D.
notableTypeOfWork
Indicates that a work is a significant or defining example within a particular type or category of work associated with an entity.
-
E.
typeOfWorkHeIsKnownFor
Indicates the category or kind of work for which a person is recognized or notable.
- 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_69e6586c14fc81908d34785f1088b0a9 |
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.