Triple
T29091112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revengers |
E734854
|
entity |
| Predicate | teamNameCoinedBy |
P30598
|
FINISHED |
| Object | Thor |
—
|
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: Thor | Statement: [Revengers, teamNameCoinedBy, Thor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamNameCoinedBy Context triple: [Revengers, teamNameCoinedBy, Thor]
-
A.
teamNameInspiredBy
chosen
Indicates that the name of one team was chosen based on, influenced by, or derived from another entity (such as a person, place, concept, or other team).
-
B.
nicknameCoinedIn
Indicates that a particular nickname was first created, introduced, or came into use in a specified time or context.
-
C.
teamName
Indicates the relationship that assigns or associates a specific name with a particular team.
-
D.
teamNameRefersTo
Indicates that a given team name designates or refers to a specific team entity.
-
E.
teamNicknamedAfter
Indicates that a team is commonly referred to by a nickname derived from or inspired by another entity.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6617d89d08190ae38220244c07b1f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 11:05 a.m.