Triple
T11960091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogers credit cards |
E284644
|
entity |
| Predicate | onlineApplication |
P102494
|
FINISHED |
| Object | available |
—
|
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: available | Statement: [Rogers credit cards, onlineApplication, available]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onlineApplication Context triple: [Rogers credit cards, onlineApplication, available]
-
A.
applicantIn
Indicates that a person or entity is serving as an applicant within a particular context, process, or organization.
-
B.
applicationProcessIncludes
Indicates that an application process contains or encompasses a specific step, component, or sub-process as part of its overall workflow.
-
C.
appliedFor
Indicates that an entity has submitted a request or application to another entity for a position, service, benefit, or opportunity.
-
D.
canApplyFor
Indicates that one entity has the eligibility or permission to submit a request or application for another entity or opportunity.
-
E.
typeOfApplication
Indicates the specific category or kind of application involved in the relationship or action.
- F. None of above. chosen
Provenance (4 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9036941948190b150369094551731 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:45 p.m.