Triple
T30744369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottsbluff complex |
E782777
|
entity |
| Predicate | hasAssociatedTechnology |
P1485
|
FINISHED |
| Object | flaked stone technology |
—
|
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: flaked stone technology | Statement: [Scottsbluff complex, hasAssociatedTechnology, flaked stone technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedTechnology Context triple: [Scottsbluff complex, hasAssociatedTechnology, flaked stone technology]
-
A.
associatedWithTechnology
chosen
Indicates a relationship where an entity is connected to, involved with, or utilizes a particular technology.
-
B.
hasTechnicalElement
Indicates that something includes, involves, or is characterized by a technical component, feature, or aspect.
-
C.
inUniverseTechnologyOf
Indicates that a technology exists within, and is part of, the fictional universe or setting associated with a given entity.
-
D.
isKeyTechnologyIn
Indicates that one technology plays a central, enabling, or foundational role within another specified context, system, or domain.
-
E.
hasInteractiveTechnology
Indicates that an entity is equipped with or incorporates technology enabling user interaction or responsive engagement.
- 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_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 29, 2026, 8:38 p.m.