Triple
T1404598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Partner of California |
E31661
|
entity |
| Predicate | isInformalTitle |
P4154
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [First Partner of California, isInformalTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInformalTitle Context triple: [First Partner of California, isInformalTitle, true]
-
A.
hasInformalStatus
chosen
Indicates that an entity holds a non-official, casual, or unofficial standing or role in relation to another entity.
-
B.
isPersonalName
Indicates that the value is a personal name identifying an individual person.
-
C.
hasOrdinaryTitle
Indicates that an entity holds a standard, non-noble or non-honorific title associated with its role or position.
-
D.
hasFormalStatus
Indicates that an entity possesses an officially recognized or legally defined status within a formal system or context.
-
E.
honorificTitle
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.