Triple
T202705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Historical Landmark |
E4539
|
entity |
| Predicate | hasCriteria |
P136
|
FINISHED |
| Object | statewide historical significance |
—
|
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: statewide historical significance | Statement: [California Historical Landmark, hasCriteria, statewide historical significance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCriteria Context triple: [California Historical Landmark, hasCriteria, statewide historical significance]
-
A.
hasCriterionType
Indicates that something is associated with or classified by a specific type of criterion used for evaluation or decision-making.
-
B.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
C.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
D.
selectionCriteria
chosen
Indicates the conditions or rules used to choose certain entities from a larger set.
-
E.
hasConformanceRequirements
Indicates that an entity is subject to specific rules, standards, or criteria that it must satisfy or comply with.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f46b4f081909e5ee3718109a71f |
completed | Feb. 28, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69a25b4b42ec8190bef16bbbdd30a742 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.