Triple
T9379754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Braid |
E225750
|
entity |
| Predicate | yearsActiveAsArchitect |
P18004
|
FINISHED |
| Object | early 1900s–mid 20th century |
—
|
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: early 1900s–mid 20th century | Statement: [James Braid, yearsActiveAsArchitect, early 1900s–mid 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearsActiveAsArchitect Context triple: [James Braid, yearsActiveAsArchitect, early 1900s–mid 20th century]
-
A.
activeInYears
Indicates that an entity was active or operational during the specified years or year range.
-
B.
architectEmployed
Indicates that an architect is employed by a particular organization, firm, or individual.
-
C.
activeYearsInCareer
chosen
Indicates the span of time during which an entity was actively engaged in a particular career or professional field.
-
D.
yearsActiveAsCoach
Indicates the span of time, typically in years, during which an individual has served in a coaching role.
-
E.
architectEngaged
Indicates that an architect has been formally hired or contracted to provide architectural services for a project or client.
- 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_69ca842d8ee88190aaaa639aa953185d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50bb49bc8190bdad23e120755ac7 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:44 p.m.