Triple
T13968996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert S. Peabody |
E336001
|
entity |
| Predicate | areaOfSupport |
P111991
|
FINISHED |
| Object | archaeological research funding |
—
|
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: archaeological research funding | Statement: [Robert S. Peabody, areaOfSupport, archaeological research funding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areaOfSupport Context triple: [Robert S. Peabody, areaOfSupport, archaeological research funding]
-
A.
supportArea
Indicates that one entity serves as a supporting region or surface that provides structural or functional backing for another entity.
-
B.
geographicAreaOfSupport
Indicates the geographic region or area within which support, assistance, or services are provided or applicable.
-
C.
affectedArea
Indicates the specific region or extent over which an event, condition, or influence has an impact.
-
D.
area of activity
Indicates the domain, field, or sphere in which an entity is active or carries out its primary functions or operations.
-
E.
areaOfService
Indicates the geographic or functional region within which a service is provided or applicable.
- F. None of above. chosen
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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e8daeac8190aadd4b3b60222482 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
| PDg | Predicate description generation | batch_69de01ed2098819088ec45069f6f2609 |
completed | April 14, 2026, 8:59 a.m. |
Created at: April 9, 2026, 10:18 p.m.