Triple
T28405515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Fellows Program |
E719514
|
entity |
| Predicate | typeOfParticipant |
P6384
|
FINISHED |
| Object | visiting fellow |
—
|
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: visiting fellow | Statement: [Global Fellows Program, typeOfParticipant, visiting fellow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfParticipant Context triple: [Global Fellows Program, typeOfParticipant, visiting fellow]
-
A.
participantType
chosen
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
B.
personType
Indicates that an entity is classified as a particular type or category of person.
-
C.
traditionalParticipantsType
Indicates the type or category of participants involved in a traditional or customary context or activity.
-
D.
supportsParticipantType
Indicates that an entity is compatible with, or designed to work with, a specified type or category of participant.
-
E.
originalParticipantsType
Indicates the type or category of participants that were initially involved in an event, action, or relationship.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: April 28, 2026, 1:23 a.m.