Triple
T32784814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California (1853–1854) |
E838464
|
entity |
| Predicate | admissionOrderInUSA |
P206
|
FINISHED |
| Object | 31 |
—
|
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: 31 | Statement: [California (1853–1854), admissionOrderInUSA, 31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admissionOrderInUSA Context triple: [California (1853–1854), admissionOrderInUSA, 31]
-
A.
admissionOrder
chosen
Indicates the sequence or priority in which admissions occur or are processed relative to one another.
-
B.
admissionRequired
Indicates that access to something is conditional on being formally admitted or granted entry beforehand.
-
C.
admissionType
Indicates the category or manner in which an entity (such as a person or case) is formally accepted or admitted into a system, institution, or process.
-
D.
admissionsSystem
Indicates a relationship where an entity functions as or is associated with a system that manages or processes admissions decisions or applications.
-
E.
admissionsBasedOn
Indicates that acceptance or entry decisions are determined according to specified criteria, factors, or conditions.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:14 a.m.