Triple
T36491789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | miniImageNet |
E899067
|
entity |
| Predicate | commonlyUsedWithWayCounts |
P198952
|
FINISHED |
| Object | 5-way |
—
|
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: 5-way | Statement: [miniImageNet, commonlyUsedWithWayCounts, 5-way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyUsedWithWayCounts Context triple: [miniImageNet, commonlyUsedWithWayCounts, 5-way]
-
A.
frequentlyUsedBy
Indicates that something is regularly or commonly utilized by a particular entity.
-
B.
streetUsage
Indicates how a street is used or intended to be used, such as for traffic, pedestrians, parking, or other specific functions.
-
C.
crossingUsedBy
Indicates that a particular crossing (such as a road, rail, or pedestrian crossing) is utilized or traversed by a specified user or traffic flow.
-
D.
usedForJourneyPlanning
Indicates that something is utilized to assist in planning or organizing a journey or trip.
-
E.
usedAsTransitRouteFor
Indicates that something serves as a pathway or channel through which another entity is transported or moved.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
| PDg | Predicate description generation | batch_69ff167608f08190b7cd2cf65ddecbf3 |
completed | May 9, 2026, 11:11 a.m. |
Created at: May 3, 2026, 4:10 p.m.