Triple
T38395520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flamsteed House (original building) |
E900750
|
entity |
| Predicate | assistantArchitect |
P30538
|
FINISHED |
| Object | Robert Hooke |
—
|
NE NERFINISHED |
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: Robert Hooke | Statement: [Flamsteed House (original building), assistantArchitect, Robert Hooke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assistantArchitect Context triple: [Flamsteed House (original building), assistantArchitect, Robert Hooke]
-
A.
principalArchitect
Indicates that one entity serves as the lead or primary architect responsible for the design or architectural direction of another entity.
-
B.
assistant
chosen
Indicates that one entity provides help, support, or services to another entity.
-
C.
terminalArchitect
Indicates a relationship where an entity serves as the final or ultimate designer or planner responsible for the structure, system, or outcome of another entity.
-
D.
possibleArchitect
Indicates that an entity is a candidate or likely creator/designer (architect) of another entity, but this authorship is not confirmed.
-
E.
usedArchitect
Indicates that one entity served as the architect responsible for designing or planning 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.