Triple
T24834926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Citizens’ Committee |
E621442
|
entity |
| Predicate | recruitedPerson |
P143089
|
FINISHED |
| Object | Homer Plessy |
—
|
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: Homer Plessy | Statement: [Citizens’ Committee, recruitedPerson, Homer Plessy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recruitedPerson Context triple: [Citizens’ Committee, recruitedPerson, Homer Plessy]
-
A.
recruitedMember
chosen
Indicates that one entity has actively enlisted, signed up, or brought another entity into a group, organization, or effort as a member.
-
B.
recruitedAs
Indicates that one entity has been brought into a role, position, or organization by another through a recruitment process.
-
C.
recruitmentFrom
Indicates that one entity recruits or sources members, employees, or participants from another entity.
-
D.
recruitsFor
Indicates that one entity actively seeks out, enlists, or brings in participants, members, or resources on behalf of another entity, such as an organization, event, or cause.
-
E.
personReferredToPosition
Indicates that one entity has been mentioned or cited as a candidate or occupant for a particular role, job, or position.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:17 a.m.