Triple
T26864289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Historic Landmarks in Arizona |
E676420
|
entity |
| Predicate | includeTypes |
P61589
|
FINISHED |
| Object | archaeological sites |
—
|
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: archaeological sites | Statement: [National Historic Landmarks in Arizona, includeTypes, archaeological sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeTypes Context triple: [National Historic Landmarks in Arizona, includeTypes, archaeological sites]
-
A.
includesFeatureTypes
Indicates that an entity contains or encompasses specific types of features as part of its composition or definition.
-
B.
includesSee
Indicates that one entity’s scope, content, or experience contains or encompasses the act of seeing or visual perception involving another entity.
-
C.
includedEntityType
chosen
Indicates that one entity type is contained within, or forms a component part of, another entity type.
-
D.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
E.
includesClasses
Indicates that one entity contains or encompasses one or more class-type entities as part of its definition or structure.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: April 27, 2026, 5:27 a.m.