Triple
T6224547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minoh City Library |
E139196
|
entity |
| Predicate | hasPrimaryUserGroup |
P17010
|
FINISHED |
| Object | local 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: local residents | Statement: [Minoh City Library, hasPrimaryUserGroup, local residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryUserGroup Context triple: [Minoh City Library, hasPrimaryUserGroup, local residents]
-
A.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
-
B.
primaryUserGroup
chosen
Indicates the main or default user group to which a user is primarily assigned or associated.
-
C.
hasCentralGroup
Indicates that an entity possesses or is associated with a primary or central group within its structure or organization.
-
D.
hasPrimaryNetwork
Indicates that an entity is associated with or connected to its main or most important network among potentially multiple networks.
-
E.
hasPrimaryHub
Indicates that an entity is associated with or operates from a main or central hub location among potentially multiple hubs.
- 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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062c214c48190b94e7f904e2bf699 |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.