Triple
T25077076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Rock |
E628078
|
entity |
| Predicate | archaeologicalFindAge |
P11951
|
FINISHED |
| Object | over 9,000 years old |
—
|
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: over 9,000 years old | Statement: [Fort Rock, archaeologicalFindAge, over 9,000 years old]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archaeologicalFindAge Context triple: [Fort Rock, archaeologicalFindAge, over 9,000 years old]
-
A.
archaeologicalEvidenceAge
chosen
Indicates the age or time period to which a piece of archaeological evidence is dated.
-
B.
approximateAgeBeforePresent
Indicates that one entity’s age is an estimated value measured as a time interval before the present moment.
-
C.
archaeologicalIdentification
Indicates the relationship by which an entity is recognized, classified, or confirmed as an archaeological object, feature, or context based on evidence or expert analysis.
-
D.
archaeologicallyExploredSince
Indicates that a place or site has been subject to archaeological exploration starting from a specified point in time.
-
E.
archaeologyAt
Indicates that an archaeological activity, study, or investigation is conducted at a specific location or site.
- 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_69f45d1ad0ec8190831b9d6d28a6644a |
completed | May 1, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:21 a.m.