Triple
T25077077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Rock |
E628078
|
entity |
| Predicate | associatedWithArchaeologist |
P78887
|
FINISHED |
| Object | Luther Cressman |
—
|
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: Luther Cressman | Statement: [Fort Rock, associatedWithArchaeologist, Luther Cressman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithArchaeologist Context triple: [Fort Rock, associatedWithArchaeologist, Luther Cressman]
-
A.
roleInArchaeology
Indicates that one entity has a specific function, position, or involvement within the field or practice of archaeology in relation to another entity.
-
B.
relatedToArchaeologicalSite
chosen
Indicates that one entity has a contextual, historical, or functional connection to an archaeological site.
-
C.
archaeologyAt
Indicates that an archaeological activity, study, or investigation is conducted at a specific location or site.
-
D.
archaeologicalCorrelation
Indicates a relationship where archaeological evidence from different sources or sites is shown to be systematically related, suggesting a meaningful connection or pattern between them.
-
E.
archaeologicalDiscipline
Indicates that one entity is an archaeological field or subfield in which the other entity (such as a person, project, or work) is specialized or involved.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:21 a.m.