Triple
T19008604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arch Manning |
E465156
|
entity |
| Predicate | recruitingRating |
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: [Arch Manning, recruitingRating, five-star recruit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recruitingRating Context triple: [Arch Manning, recruitingRating, 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.
recruitingFocus
Indicates that an entity’s recruitment efforts are specifically directed toward or concentrated on another entity or group.
-
D.
recruitmentBasis
Indicates the criteria, grounds, or conditions on which an entity is recruited or selected for a role or position.
-
E.
recruitingProfile
Indicates that an entity serves as or is associated with a recruiting profile used for hiring or talent acquisition activities.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6a72aa88190a04f13cd14ee77d4 |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.