Triple
T25986967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Walking Dead #100 |
E646227
|
entity |
| Predicate | teamOrGroupFeatured |
P5852
|
FINISHED |
| Object | Rick Grimes' survivor group |
—
|
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: Rick Grimes' survivor group | Statement: [The Walking Dead #100, teamOrGroupFeatured, Rick Grimes' survivor group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamOrGroupFeatured Context triple: [The Walking Dead #100, teamOrGroupFeatured, Rick Grimes' survivor group]
-
A.
hostedTeamOrGroup
Indicates that one entity serves as the host or organizing body for a particular team or group.
-
B.
teammateGroup
Indicates that multiple entities are members of the same team or collaborative group.
-
C.
featuredTeam
chosen
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
D.
organizedTeam
Indicates that an entity has formed, structured, or coordinated a group of individuals to function together as a team.
-
E.
teamBasedOn
Indicates that one entity (typically a team) is formed, organized, or defined on the basis of another entity (such as a criterion, source, or underlying structure).
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605446ca48190907baef523f13ccf |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 8:55 a.m.