Triple
T9693461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basketmaker II period |
E234590
|
entity |
| Predicate | hasKeySubsistenceItem |
P4849
|
FINISHED |
| Object | maize |
—
|
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: maize | Statement: [Basketmaker II period, hasKeySubsistenceItem, maize]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeySubsistenceItem Context triple: [Basketmaker II period, hasKeySubsistenceItem, maize]
-
A.
hasKeyQuantity
Indicates that an entity is associated with a primary or defining quantity that characterizes or measures it.
-
B.
hasKeyResource
chosen
Indicates that an entity possesses or depends on a critical resource necessary for its function, operation, or success.
-
C.
hasKeyPassage
Indicates that one entity contains or includes a particularly important or central passage relevant to another entity.
-
D.
hasKeyWork
Indicates that an entity possesses or is associated with a primary or central work (such as a main publication, artwork, or project) that is especially representative or important.
-
E.
hasKeyArtifact
Indicates that an entity possesses or is associated with a crucial or central artifact relevant to a particular context or process.
- 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d0727908190897894151c0ee7c2 |
completed | April 1, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:17 p.m.