Triple
T855265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapman’s Court |
E18477
|
entity |
| Predicate | hasPrimaryUsers |
P2090
|
FINISHED |
| Object | Emmanuel College undergraduates |
—
|
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: Emmanuel College undergraduates | Statement: [Chapman’s Court, hasPrimaryUsers, Emmanuel College undergraduates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryUsers Context triple: [Chapman’s Court, hasPrimaryUsers, Emmanuel College undergraduates]
-
A.
hasUser
Indicates that an entity is associated with or linked to a specific user.
-
B.
hasPrimarySee
Indicates that one entity is designated as the main or preferred "see" reference or cross-reference for another entity.
-
C.
primaryUser
chosen
Indicates that the referenced user is the main or principal user associated with a given account, resource, or context.
-
D.
hasUserService
Indicates that an entity is associated with or utilizes a particular user-related service.
-
E.
hasPrimaryPlatform
Indicates that one entity is designated as the main or principal platform associated with another 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac3a48c08190b4677d825fcbfaf9 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa834a588190bca4a0eb83fb3eb6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.