Triple
T9383224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge Mill |
E225837
|
entity |
| Predicate | hasRestorationStatus |
P71735
|
FINISHED |
| Object | restored |
—
|
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: restored | Statement: [Cambridge Mill, hasRestorationStatus, restored]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRestorationStatus Context triple: [Cambridge Mill, hasRestorationStatus, restored]
-
A.
hasRestoration
Indicates that an entity has undergone, is undergoing, or is associated with a process of repair, renewal, or restoration.
-
B.
hasRestorationActivities
Indicates that an entity carries out, is involved in, or is associated with actions aimed at restoring or rehabilitating another entity or resource.
-
C.
hasBeenRestored
chosen
Indicates that an entity has been returned to a previous or original state after damage, loss, or alteration.
-
D.
hasRestorationFocus
Indicates that something is primarily concerned with or directed toward restoration or repair.
-
E.
hasRemediationStatus
Indicates the current state or progress of remediation efforts applied to an identified issue, risk, or non-compliance.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50c11d648190b03cedbce0b72c60 |
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.