Triple
T661752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Community Reinvestment Act |
E11769
|
entity |
| Predicate | performanceRatingScale |
P8710
|
FINISHED |
| Object | Outstanding |
—
|
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: Outstanding | Statement: [Community Reinvestment Act, performanceRatingScale, Outstanding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceRatingScale Context triple: [Community Reinvestment Act, performanceRatingScale, Outstanding]
-
A.
rating
chosen
Indicates an evaluation relationship where one entity assigns a qualitative or quantitative score or judgment to another entity.
-
B.
scoring
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
-
C.
payGrade
Indicates the level or category of compensation assigned to an entity, typically reflecting its rank, role, or seniority in a pay structure.
-
D.
gradeRank
Indicates the relative academic standing or position of an entity within a graded or ranked group based on performance or scores.
-
E.
rankingBasis
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fa954988190841740a587ace466 |
completed | March 1, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69a49d153a948190b3ccdc331ed33617 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.