Triple
T12633102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinjuku Ward Central Library |
E301691
|
entity |
| Predicate | mainUsers |
P7221
|
FINISHED |
| Object | Shinjuku residents |
—
|
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: Shinjuku residents | Statement: [Shinjuku Ward Central Library, mainUsers, Shinjuku residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainUsers Context triple: [Shinjuku Ward Central Library, mainUsers, Shinjuku residents]
-
A.
otherUsers
Indicates a relationship where one or more users are distinguished as being different from a given primary or reference user.
-
B.
userBase
chosen
Indicates that one entity serves as the primary or foundational group of users associated with another entity.
-
C.
traditionalUsers
Indicates that the associated users adhere to long-established or customary practices, methods, or preferences in the given context.
-
D.
primaryUsersRole
Indicates the role that a primary user holds in relation to a given resource, system, or context.
-
E.
dataUsers
Indicates a relationship where certain entities use, access, or consume specific data.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:15 p.m.