Triple
T9504553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Orpington |
E229229
|
entity |
| Predicate | standardVarietyStatus |
P8040
|
FINISHED |
| Object | standardized |
—
|
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: standardized | Statement: [Blue Orpington, standardVarietyStatus, standardized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardVarietyStatus Context triple: [Blue Orpington, standardVarietyStatus, standardized]
-
A.
standardVarietyBasedIn
Indicates that a standard or reference variety (such as a language or dialect) is primarily established, recognized, or centered in a particular location or region.
-
B.
standardState
Indicates that an entity is in its default, reference, or officially recognized condition or configuration under standard conditions.
-
C.
standardizationStatus
chosen
Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
-
D.
canonicalStatus
Indicates the formal or official standing of an entity within an established authoritative or normative system.
-
E.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9850fe6c8190a5a96cfae12562c6 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:57 p.m.