Triple
T31306250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Oklahoma archaeologists |
E798342
|
entity |
| Predicate | conductFieldworkIn |
P49766
|
FINISHED |
| Object | Oklahoma |
—
|
NE NERFINISHED |
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: Oklahoma | Statement: [University of Oklahoma archaeologists, conductFieldworkIn, Oklahoma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conductFieldworkIn Context triple: [University of Oklahoma archaeologists, conductFieldworkIn, Oklahoma]
-
A.
hasConductedFieldworkOn
Indicates that an agent has performed research or investigative fieldwork focused on a particular subject, location, or population.
-
B.
associatedFieldworkSource
Indicates that something is linked to, derived from, or documented by a particular piece of fieldwork or fieldwork data source.
-
C.
coSurveyedWith
Indicates that two or more entities participated together in the same survey activity or data-collection effort.
-
D.
placeOfFieldwork
chosen
Indicates the location where a person conducts or has conducted their fieldwork activities.
-
E.
conductsResearchAt
Indicates that a subject carries out research activities at a specified institution, organization, or location.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:14 p.m.