Triple
T9158829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cumberland culture |
E219770
|
entity |
| Predicate | toolType |
P86841
|
FINISHED |
| Object | Cumberland point |
—
|
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: Cumberland point | Statement: [Cumberland culture, toolType, Cumberland point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toolType Context triple: [Cumberland culture, toolType, Cumberland point]
-
A.
toolIn
Indicates that one entity is a tool or instrument used in or associated with another entity or context.
-
B.
toolDescribed
Indicates that one entity provides a description or explanation of a tool associated with another entity.
-
C.
toolUsed
Indicates that an action or task is performed using a particular tool as the means or instrument.
-
D.
typicalTools
Indicates that the related tools are commonly or characteristically used to perform the associated activity, task, or function.
-
E.
toolMentioned
Indicates that a particular tool is referenced or brought up in the given context or interaction.
- F. None of above. chosen
Provenance (4 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_69ca83e25418819093c6503deeaf30de |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca9d805588190a0deadda1dd410a1 |
completed | April 1, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc668ad3d881908a8a93a6a1d553e4 |
completed | April 1, 2026, 12:27 a.m. |
Created at: March 30, 2026, 7:21 p.m.