Triple
T18947846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troy Bowles |
E463561
|
entity |
| Predicate | hasRecruitStatus |
P133905
|
FINISHED |
| Object | notable college recruit |
—
|
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: notable college recruit | Statement: [Troy Bowles, hasRecruitStatus, notable college recruit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecruitStatus Context triple: [Troy Bowles, hasRecruitStatus, notable college recruit]
-
A.
hasRecruitType
Indicates that an entity is associated with a specific type or category of recruitment.
-
B.
hasVolunteerStatus
Indicates that an entity holds a particular volunteer-related status or role within a specified context.
-
C.
isRecruitableCharacter
Indicates that a character can be obtained and added to the player’s controllable roster or party.
-
D.
hasWorkStatus
Indicates the current employment or occupational state associated with an entity, such as whether it is active, inactive, or in a specific work condition.
-
E.
hasEarlyRecruitmentBase
Indicates that an entity has an initial or foundational group from which it recruits members or participants earlier than usual in a process or timeline.
- F. None of above. chosen
Provenance (4 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d540e57c8190bb17fff6d4254320 |
completed | April 20, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 11:59 a.m.