Triple
T30744508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom D. Dillehay |
E782781
|
entity |
| Predicate | notableWorkSite |
P90664
|
FINISHED |
| Object | Monte Verde archaeological site |
E219771
|
NE 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: Monte Verde archaeological site | Statement: [Tom D. Dillehay, notableWorkSite, Monte Verde archaeological site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkSite Context triple: [Tom D. Dillehay, notableWorkSite, Monte Verde archaeological site]
-
A.
notablePlaceOfWork
chosen
Indicates that there is a notable or significant place where the entity has worked or been employed.
-
B.
notableSite
Indicates that a site holds particular significance, prominence, or recognition in some context.
-
C.
notableSiteFor
Indicates that a site is particularly recognized or distinguished for a specific feature, activity, event, or characteristic.
-
D.
notableSiteType
Indicates that a site is notable specifically for being of a particular type or category (e.g., a notable example of that kind of site).
-
E.
notableSiteListedOn
Indicates that a notable site is recorded or referenced within a particular list, registry, or catalog.
- F. None of above.
Provenance (4 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28b08c87408190be94f468b41a9599 |
completed | June 10, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:38 p.m.