Triple
T37713717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Amazing Spider-Man #129 |
E939404
|
entity |
| Predicate | featuresTeamOrOrganization |
P204355
|
FINISHED |
| Object | Daily Bugle |
E120785
|
NE 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: Daily Bugle | Statement: [The Amazing Spider-Man #129, featuresTeamOrOrganization, Daily Bugle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTeamOrOrganization Context triple: [The Amazing Spider-Man #129, featuresTeamOrOrganization, Daily Bugle]
-
A.
featuresTeamUp
Indicates that two or more entities collaborate or join forces to act together as a team.
-
B.
featuresTeams
Indicates that something prominently presents or includes specific teams as a central element or focus.
-
C.
featuresTeamLevel
Indicates that a feature is available or applicable at the team (rather than individual or organization) level.
-
D.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
E.
fieldsTeam
Indicates that an entity is a member of, or associated as part of, a particular team.
- F. None of above. chosen
Provenance (5 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40cdd5cd5081909eb9b9c27be4793b |
completed | June 28, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.