Triple
T19662212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GPT-4.1-mini |
E472108
|
entity |
| Predicate | capabilityLevel |
P33687
|
FINISHED |
| Object | mid-tier within GPT-4.1 family |
—
|
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: mid-tier within GPT-4.1 family | Statement: [GPT-4.1-mini, capabilityLevel, mid-tier within GPT-4.1 family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capabilityLevel Context triple: [GPT-4.1-mini, capabilityLevel, mid-tier within GPT-4.1 family]
-
A.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
B.
consideredCapability
Indicates that something is regarded or evaluated as a potential capability of an entity.
-
C.
qualificationLevel
Indicates the degree or rank of competence, certification, or formal credentials required for or possessed in relation to something.
-
D.
demonstratedCapability
Indicates that an entity has shown, through evidence or performance, the ability to carry out a specific action or function.
-
E.
configurationLevel
chosen
Indicates the degree or tier of settings or parameters applied to configure something within a system or context.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6414b30fc81908e6594ba8f2d2942 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.