Triple
T20610569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | StreetPass |
E506435
|
entity |
| Predicate | encounterLimitPerDay |
P83413
|
FINISHED |
| Object | some titles limit number of StreetPass hits per day |
—
|
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: some titles limit number of StreetPass hits per day | Statement: [StreetPass, encounterLimitPerDay, some titles limit number of StreetPass hits per day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encounterLimitPerDay Context triple: [StreetPass, encounterLimitPerDay, some titles limit number of StreetPass hits per day]
-
A.
dailyQuota
chosen
Indicates the maximum amount or limit allocated or allowed for an entity within a single day.
-
B.
minimumSessionsPerYear
Indicates the smallest number of sessions that must occur within a one-year period.
-
C.
countInDayApprox
Indicates an approximate number of times an event or relation occurs within a single day.
-
D.
attemptLimit
Indicates a restriction on how many times an action or operation may be attempted before it is stopped or blocked.
-
E.
rideLimit
Indicates a constraint on the maximum number, duration, or frequency of rides permitted for an entity.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aad6f53481908fb242947dda7028 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.