Triple
T12753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California poppy |
E256
|
entity |
| Predicate | originOfName |
P453
|
FINISHED |
| Object | named after California |
—
|
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: named after California | Statement: [California poppy, originOfName, named after California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originOfName Context triple: [California poppy, originOfName, named after California]
-
A.
etymology
chosen
Indicates the historical origin and development of a word or term, including its source language and form.
-
B.
ethnicOrigin
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
C.
etymologicalLanguage
Indicates the language from which a word or term is historically derived in its etymology.
-
D.
givenName
Indicates the personal first name assigned to an individual.
-
E.
namesakeOccupation
Indicates that one entity’s occupation is the same as, or derived from, the occupation associated with the other entity’s namesake.
- 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a243abb2ec8190937365e5ecec52ad |
completed | Feb. 28, 2026, 1:23 a.m. |
| PD | Predicate disambiguation | batch_69a23fe9470c8190918a6ca1df168646 |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.