Triple
T30744342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick complex |
E782776
|
entity |
| Predicate | hasResearchDomain |
P934
|
FINISHED |
| Object | Plains archaeology |
—
|
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: Plains archaeology | Statement: [Frederick complex, hasResearchDomain, Plains archaeology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResearchDomain Context triple: [Frederick complex, hasResearchDomain, Plains archaeology]
-
A.
hasResearchArea
chosen
Indicates that an entity (such as a person, project, or organization) is associated with or focused on a particular field or area of research.
-
B.
hasResearchComponent
Indicates that an entity includes, involves, or is associated with a research-related component or activity.
-
C.
hasResearcher
Indicates that an entity is associated with or linked to a specific researcher responsible for work, study, or investigation related to it.
-
D.
isInResearchArea
Indicates that one entity falls within, or is relevant to, the specified research area of another entity.
-
E.
hasTypeOfResearch
Indicates that an entity is associated with a particular category or kind of research it involves or conducts.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00ac5654a0819090701f61a5802d64 |
completed | May 10, 2026, 4:03 p.m. |
| PD | Predicate disambiguation | batch_6a00ab94b5e881909e15d1342e5f43be |
completed | May 10, 2026, 4 p.m. |
Created at: April 29, 2026, 8:38 p.m.