Triple
T28921923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Team |
E733535
|
entity |
| Predicate | typicalExcavationDuration |
P99908
|
FINISHED |
| Object | three days |
—
|
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: three days | Statement: [Time Team, typicalExcavationDuration, three days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalExcavationDuration Context triple: [Time Team, typicalExcavationDuration, three days]
-
A.
timeSpanOfExcavations
chosen
Indicates the duration or period of time during which the excavations took place.
-
B.
excavationProject
Indicates that an entity is involved in or constitutes a project whose primary activity is the systematic excavation of a site or area.
-
C.
excavationYear
Indicates the year in which an excavation activity took place or was conducted.
-
D.
excavationSite
Indicates a location where digging or removal of earth or materials is actively conducted, typically for construction, mining, or archaeological purposes.
-
E.
excavationType
Indicates the specific method or category of excavation associated with an entity or activity.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a013c50bcb8819086d163f1a796a9b8 |
completed | May 11, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_6a013c01bac88190b15c70910c02a8a7 |
completed | May 11, 2026, 2:16 a.m. |
Created at: April 28, 2026, 8:20 a.m.