Triple
T36303873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawkette |
E893892
|
entity |
| Predicate | usedByTeamMemberOf |
P129160
|
FINISHED |
| Object | Young Avengers |
—
|
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: Young Avengers | Statement: [Hawkette, usedByTeamMemberOf, Young Avengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByTeamMemberOf Context triple: [Hawkette, usedByTeamMemberOf, Young Avengers]
-
A.
usedByTeam
Indicates that something (such as a resource, tool, or method) is utilized or employed by a particular team.
-
B.
associatedWithTeamMember
chosen
Indicates a relationship where an entity has a connection, involvement, or linkage with a specific member of a team.
-
C.
usedByTeams
Indicates that something (such as a tool, resource, or process) is utilized or employed by one or more teams.
-
D.
usedForTeam
Indicates that something is utilized or designated for use by a particular team.
-
E.
hasTeamMember
Indicates that an entity includes another entity as a member of its team.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:09 p.m.