Triple
T36733881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Ternan |
E907412
|
entity |
| Predicate | researchFieldAssociated |
P148667
|
FINISHED |
| Object | paleoanthropology |
—
|
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: paleoanthropology | Statement: [Fort Ternan, researchFieldAssociated, paleoanthropology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: researchFieldAssociated Context triple: [Fort Ternan, researchFieldAssociated, paleoanthropology]
-
A.
associatedScholarlyField
chosen
Indicates that one entity is connected to or concerned with a particular scholarly or academic field of study.
-
B.
relatedWorkField
Indicates that one work is associated with or pertains to the same or a relevant field, discipline, or area of activity as another work.
-
C.
researchFocusSince
Indicates the point in time since which an entity has maintained a particular research focus or area of study.
-
D.
academicFieldOfAuthor
Indicates the academic discipline or field in which an author conducts their scholarly work or produces publications.
-
E.
researchUser
Indicates that an entity conducts research on, studies, or investigates a particular user.
- 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_69f76e75aa6881909b844d00a3888ee5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.