Triple
T29767007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contractors Hill |
E753940
|
entity |
| Predicate | wasModifiedDuring |
P98606
|
FINISHED |
| Object | early 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 20th century | Statement: [Contractors Hill, wasModifiedDuring, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasModifiedDuring Context triple: [Contractors Hill, wasModifiedDuring, early 20th century]
-
A.
modifiedDuring
chosen
Indicates that one entity underwent a change or alteration while another specified time period, process, or event was occurring.
-
B.
isModifiedAs
Indicates that an entity has been altered or changed from its original state in some specified manner.
-
C.
hasHumanModification
Indicates that an entity has been altered, influenced, or modified as a result of human activity or intervention.
-
D.
laterModifiedIn
Indicates that one entity was modified at a later time than another entity within the same context or sequence.
-
E.
changedAfter
Indicates that one entity underwent a change at a point in time that is later than the time at which another referenced entity changed.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6745d64ec8190a4726ed224b82873 |
completed | May 2, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 8:38 p.m.