Triple
T25480195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harriet |
E638547
|
entity |
| Predicate | excavationEnvironment |
P158589
|
FINISHED |
| Object | underwater conditions |
—
|
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: underwater conditions | Statement: [Harriet, excavationEnvironment, underwater conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excavationEnvironment Context triple: [Harriet, excavationEnvironment, underwater conditions]
-
A.
excavationEnvironment
chosen
Indicates the environmental conditions or setting in which an excavation activity takes 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.
excavationType
Indicates the specific method or category of excavation associated with an entity or activity.
-
D.
excavationSite
Indicates a location where digging or removal of earth or materials is actively conducted, typically for construction, mining, or archaeological purposes.
-
E.
excavationIntensified
Indicates that the level or extent of excavation activity has increased in intensity compared to a previous state or period.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f775776881909086b4249307c522 |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:30 p.m.