Triple
T10813865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Bar of Texas |
E255172
|
entity |
| Predicate | barAssociationType |
P20417
|
FINISHED |
| Object | unified bar |
—
|
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: unified bar | Statement: [State Bar of Texas, barAssociationType, unified bar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: barAssociationType Context triple: [State Bar of Texas, barAssociationType, unified bar]
-
A.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
B.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
-
C.
bandAssociation
Indicates a relationship where an entity is associated with, belongs to, or is affiliated with a particular band or musical group.
-
D.
leaderAssociatedWith
Indicates a relationship where a leader is connected or affiliated with a particular entity, such as an organization, group, or cause.
-
E.
linkType
chosen
Indicates the specific kind or category of relationship that connects two linked entities.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733eba9b48190b4dbe7fe5d8be0a4 |
completed | April 9, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:18 p.m.