Triple
T12072333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hub |
E287453
|
entity |
| Predicate | notableContributorRole |
P11898
|
FINISHED |
| Object | civil rights advocate |
—
|
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: civil rights advocate | Statement: [The Hub, notableContributorRole, civil rights advocate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableContributorRole Context triple: [The Hub, notableContributorRole, civil rights advocate]
-
A.
notableWorkRole
Indicates that a person’s role or position is specifically associated with the creation, performance, or contribution to a notable work.
-
B.
notableContribution
Indicates that an entity has made a significant, recognized contribution to another entity, field, work, or endeavor.
-
C.
notableAuthorMember
Indicates that an entity is a notable or distinguished author who is a member of a particular group, organization, or collection.
-
D.
notableContributionField
chosen
Indicates the field or domain in which an entity has made a significant or noteworthy contribution.
-
E.
notableParticipant
Indicates that an entity plays a significant or distinguished role as a participant in an event, activity, or context.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bda47c8190b94860b31df4a98c |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:48 p.m.