Triple
T19128311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walker and Weeks |
E468243
|
entity |
| Predicate | hasWorkInSector |
P17879
|
FINISHED |
| Object | civic architecture |
—
|
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: civic architecture | Statement: [Walker and Weeks, hasWorkInSector, civic architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkInSector Context triple: [Walker and Weeks, hasWorkInSector, civic architecture]
-
A.
hasOccupationSector
Indicates that an entity’s occupation belongs to or is categorized within a particular economic or professional sector.
-
B.
hasWorksIn
Indicates that one entity is employed by or performs their professional activities within the organization, location, or context represented by another entity.
-
C.
hasWorkedIn
chosen
Indicates that a person has been employed or has performed work within a particular organization, location, or domain for some period of time.
-
D.
hasIndustryRole
Indicates that an entity holds or performs a specific role, function, or position within a particular industry or sector.
-
E.
hasWorkedFor
Indicates that an entity has been employed by or has provided work or services to another 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ceb5808190b3b53d9e8df3605a |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.