Triple
T38069663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nova (Frankie Raye) |
E950559
|
entity |
| Predicate | notableTeamUp |
P8554
|
FINISHED |
| Object | Silver Surfer |
E282423
|
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: Silver Surfer | Statement: [Nova (Frankie Raye), notableTeamUp, Silver Surfer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTeamUp Context triple: [Nova (Frankie Raye), notableTeamUp, Silver Surfer]
-
A.
notableMultipleTeamChampion
Indicates that an entity has won championship titles with multiple different teams.
-
B.
notableCollaboration
chosen
Indicates a significant joint effort or partnership between entities that produced a noteworthy shared outcome or work.
-
C.
notableTeamUnit
Indicates that an entity is a significant or distinguished member unit (such as a player or component) of a particular team.
-
D.
notableTeammate
Indicates that one entity has a teammate relationship with another entity who is particularly prominent, distinguished, or noteworthy.
-
E.
notableTeamType
Indicates that an entity is notably associated with a team of a specified type (e.g., national team, club team, or other team category).
- F. None of above.
Provenance (4 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a42341745f88190941de473da83917e |
completed | June 29, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.