Triple
T35481302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago legal community |
E1025476
|
entity |
| Predicate | hasMajorBarAssociation |
P203859
|
FINISHED |
| Object | Chicago Bar Association |
E1554803
|
NE 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: Chicago Bar Association | Statement: [Chicago legal community, hasMajorBarAssociation, Chicago Bar Association]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorBarAssociation Context triple: [Chicago legal community, hasMajorBarAssociation, Chicago Bar Association]
-
A.
hasMajor
Indicates that an entity (typically a person or student) has a specific primary field of academic study or specialization.
-
B.
hasMajorCategory
Indicates that something is associated with or classified under a primary, overarching category.
-
C.
hasMajorBay
Indicates that an entity possesses or is associated with a primary or significant bay.
-
D.
hasMajorBranch
Indicates that one entity possesses or includes another entity as a primary or principal subdivision or branch.
-
E.
hasMajorBaseAmong
Indicates that one entity has its primary or most significant base of operations located within or among another entity or group.
- F. None of above. chosen
Provenance (5 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0226c8b2f881909de3c1a5ba40fc49 |
completed | May 11, 2026, 6:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38403f9c448190ad45f69aa7f68309 |
completed | June 21, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_6a0225602acc8190978ab4aacc615b8d |
completed | May 11, 2026, 6:52 p.m. |
| PDg | Predicate description generation | batch_6a0226c7f31c819093c2049efccbacbc |
completed | May 11, 2026, 6:58 p.m. |
Created at: May 3, 2026, 4:04 p.m.