Triple
T20610568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | StreetPass |
E506435
|
entity |
| Predicate | supportsMultipleEncounters |
P62241
|
FINISHED |
| Object | can store multiple recent encounters per title |
—
|
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: can store multiple recent encounters per title | Statement: [StreetPass, supportsMultipleEncounters, can store multiple recent encounters per title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMultipleEncounters Context triple: [StreetPass, supportsMultipleEncounters, can store multiple recent encounters per title]
-
A.
supportsMultipleMatches
Indicates that the relationship or operation can involve or return more than one matching counterpart rather than being limited to a single match.
-
B.
supportsMultipleOffensesPerIncident
Indicates that a single incident can be associated with, or give rise to, more than one distinct offense.
-
C.
hasMultiple
chosen
Indicates that an entity is associated with more than one instance or occurrence of another related entity.
-
D.
hasEncounter
Indicates that one entity experiences or comes into contact with another entity or event, typically in a specific context or situation.
-
E.
multipleAccess
Indicates that an entity can be accessed or used by more than one agent, user, or process, either simultaneously or sequentially.
- 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.