Triple
T35673267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Josh Hendricks |
E1030781
|
entity |
| Predicate | participatedInOrganization |
P146201
|
FINISHED |
| Object | UFC |
—
|
NE NERFINISHED |
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: UFC | Statement: [Josh Hendricks, participatedInOrganization, UFC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participatedInOrganization Context triple: [Josh Hendricks, participatedInOrganization, UFC]
-
A.
appearsInOrganization
chosen
Indicates that an entity is present, featured, or participates within a particular organization.
-
B.
worksInOrganizationType
Indicates that an entity is employed by or performs work within an organization of a specified type (e.g., company, nonprofit, government agency).
-
C.
representedOrganization
Indicates that one entity acts on behalf of, or serves as the official representative of, another organization.
-
D.
collaboratingOrganization
Indicates that two organizations are working together in a coordinated way toward shared goals, projects, or activities.
-
E.
subjectOrganization
Indicates that one entity serves as the organization to which another entity (such as a person, work, or activity) is affiliated or belongs.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:05 p.m.