Triple
T18238175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natural History |
E436734
|
entity |
| Predicate | coversFieldwork |
P113310
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Natural History, coversFieldwork, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversFieldwork Context triple: [Natural History, coversFieldwork, true]
-
A.
hasConductedFieldworkOn
Indicates that an agent has performed research or investigative fieldwork focused on a particular subject, location, or population.
-
B.
associatedFieldworkSource
chosen
Indicates that something is linked to, derived from, or documented by a particular piece of fieldwork or fieldwork data source.
-
C.
placeOfFieldwork
Indicates the location where a person conducts or has conducted their fieldwork activities.
-
D.
coversField
Indicates that one entity extends over, protects, or occupies the surface or area of a field associated with another entity.
-
E.
fieldOfWork
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
- 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f7e0a0ac819090d48ae45b1ebfc9 |
completed | April 19, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:33 a.m.