Triple
T10889806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewry Wall |
E257143
|
entity |
| Predicate | majorExcavationsStartDate |
P7651
|
FINISHED |
| Object | 1936 |
—
|
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: 1936 | Statement: [Jewry Wall, majorExcavationsStartDate, 1936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorExcavationsStartDate Context triple: [Jewry Wall, majorExcavationsStartDate, 1936]
-
A.
majorExcavationsBegan
chosen
Indicates that significant archaeological or construction excavation work was initiated at a particular time or for a particular project.
-
B.
majorExcavationEndYear
Indicates the year in which a major excavation activity or project was completed.
-
C.
firstExcavationYear
Indicates the calendar year in which an excavation activity at a given site or object was first carried out.
-
D.
laterExcavationDate
Indicates that one excavation event occurred at a later date than another excavation event.
-
E.
hasArchaeologicalExcavationsSince
Indicates that archaeological excavations have been conducted at an entity starting from a specified point in time and continuing since then.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d752041e2c8190b513dc9dc5857fcc |
completed | April 9, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.