Triple
T71916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieutenant Governor of California |
E1438
|
entity |
| Predicate | canBeFromDifferentPartyThan |
P3583
|
FINISHED |
| Object | Governor of 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: Governor of California | Statement: [Lieutenant Governor of California, canBeFromDifferentPartyThan, Governor of California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeFromDifferentPartyThan Context triple: [Lieutenant Governor of California, canBeFromDifferentPartyThan, Governor of California]
-
A.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
B.
negotiatingParty
Indicates that an entity is actively involved as a participant in a negotiation process with another entity.
-
C.
isDistinctFrom
Indicates that two entities are not identical and can be clearly distinguished from one another.
-
D.
canAlsoBe
Indicates that something has an additional possible state, role, or classification beyond its primary one.
-
E.
isSharedBy
Indicates that something is jointly possessed, used, or experienced by two or more entities.
- F. None of above. chosen
Provenance (4 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_69a24c06b3bc8190aa4ac89026115efc |
completed | Feb. 28, 2026, 1:59 a.m. |
| NER | Named-entity recognition | batch_69a24f6997c081908b202f937eb2b14f |
completed | Feb. 28, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69a24eab7f408190a8275cb82474f575 |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a24f65170c8190bc541c8351456a4d |
completed | Feb. 28, 2026, 2:13 a.m. |
Created at: Feb. 28, 2026, 2:03 a.m.