Triple
T12945188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAMELS rating system |
E309741
|
entity |
| Predicate | expandedToCAMELS |
P11669
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [CAMELS rating system, expandedToCAMELS, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedToCAMELS Context triple: [CAMELS rating system, expandedToCAMELS, 1990s]
-
A.
expandedAs
Indicates that one entity is a more detailed, elaborated, or fully written-out form of another, capturing how the latter is expanded from the former.
-
B.
expandsTo
chosen
Indicates that one entity unfolds, develops, or is elaborated into another, typically more detailed or extensive, representation or form.
-
C.
expandedBy
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
D.
expandedToForm
Indicates that something increased in size, scope, or extent until it took on or resulted in a particular form or configuration.
-
E.
expandableTo
Indicates that one entity can be extended, enlarged, or developed to become or accommodate 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.