Triple
T7304767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California State Treasurer’s Office |
E167945
|
entity |
| Predicate | typeOfBondManaged |
P49770
|
FINISHED |
| Object | general obligation bonds |
—
|
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: general obligation bonds | Statement: [California State Treasurer’s Office, typeOfBondManaged, general obligation bonds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBondManaged Context triple: [California State Treasurer’s Office, typeOfBondManaged, general obligation bonds]
-
A.
hasBondType
chosen
Indicates the specific kind of bond or connection that exists between two related entities.
-
B.
typeOfPropertyManaged
Indicates the specific category or kind of property that an entity is responsible for managing.
-
C.
bondedWith
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
D.
hasTypeOfManagement
Indicates that an entity is associated with or operates under a specified form or style of management.
-
E.
bondedWithSpecies
Indicates a relationship where an entity has formed a close, enduring bond or attachment with a particular species.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebd61c0c8190abb1368c9dfb1550 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.