Triple
T25683515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAT |
E644002
|
entity |
| Predicate | scoreReport |
P16725
|
FINISHED |
| Object | percentile-based performance indicator |
—
|
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: percentile-based performance indicator | Statement: [CAT, scoreReport, percentile-based performance indicator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoreReport Context triple: [CAT, scoreReport, percentile-based performance indicator]
-
A.
scoreReportedTo
Indicates that a score or result has been communicated or submitted from one party to another.
-
B.
scores
Indicates that one entity achieves or is assigned a numerical result, rating, or points in relation to another entity, such as a test, game, or evaluation.
-
C.
scoreScale
chosen
Indicates the scale or range on which a score or rating is expressed or measured.
-
D.
individualScoring
Indicates that a specific individual receives or is assigned a particular score or evaluation in a given context.
-
E.
reportsOutcomeOf
Indicates that one entity communicates or provides the result, consequence, or final status of another entity’s process, event, or action.
- 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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb7b3d008190ab61ce5c33893540 |
completed | May 2, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 8:04 p.m.