Triple
T29526032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doc Savage Magazine |
E749070
|
entity |
| Predicate | heroTeamMembersFeatured |
P129134
|
FINISHED |
| Object | Monk Mayfair |
—
|
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: Monk Mayfair | Statement: [Doc Savage Magazine, heroTeamMembersFeatured, Monk Mayfair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroTeamMembersFeatured Context triple: [Doc Savage Magazine, heroTeamMembersFeatured, Monk Mayfair]
-
A.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
B.
AllStarTeam
Indicates that an entity has been selected for inclusion on an all-star team, recognizing it as one of the top performers within a league, season, or competition.
-
C.
featuresCharactersFrom
Indicates that one entity (such as a work or production) includes or presents characters originating from another entity.
-
D.
featuresTeams
Indicates that something prominently presents or includes specific teams as a central element or focus.
-
E.
mainProtagonistTeamMember
chosen
Indicates that an entity is a member of the primary team or group associated with the main protagonist.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c9d5df48190ad10afb467a9c7a6 |
completed | May 2, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:46 p.m.