Triple
T15044373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JCR |
E379184
|
entity |
| Predicate | mayAffiliatedWith |
P55963
|
FINISHED |
| Object | college student union |
—
|
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: college student union | Statement: [JCR, mayAffiliatedWith, college student union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayAffiliatedWith Context triple: [JCR, mayAffiliatedWith, college student union]
-
A.
allowsAffiliationOf
Indicates that one entity grants permission or enables another entity to establish or hold an affiliation with it.
-
B.
possibleAffiliation
chosen
Indicates that there is a potential or uncertain organizational, group, or institutional association between the entities, but the affiliation is not confirmed.
-
C.
commonAffiliation
Indicates that two or more entities share the same organizational, institutional, or group affiliation.
-
D.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
E.
holderAffiliation
Indicates that a holder (such as a person or organization) is affiliated with, or belongs to, a particular group, institution, or 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded830c3c08190a87b81abbbb75377 |
completed | April 15, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 3 a.m.