Triple
T8811215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin Knox |
E209663
|
entity |
| Predicate | recruitingRank |
P69444
|
FINISHED |
| Object | five-star 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: five-star recruit | Statement: [Kevin Knox, recruitingRank, five-star recruit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recruitingRank Context triple: [Kevin Knox, recruitingRank, five-star recruit]
-
A.
recruitingRanking
chosen
Indicates the relative standing or quality level assigned to an entity based on its effectiveness or success in recruiting participants, members, or talent.
-
B.
recruitingReputation
Indicates the perceived quality or effectiveness of an entity’s ability to attract and hire desirable candidates.
-
C.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
D.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
E.
springRank
Indicates a ranking relationship where entities are ordered or positioned relative to each other based on a spring-like or force-directed hierarchy or influence measure.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fed18f8819087b0282bf8c4208c |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.