Triple
T29091126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revengers |
E734854
|
entity |
| Predicate | temporaryTeam |
P29740
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Revengers, temporaryTeam, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporaryTeam Context triple: [Revengers, temporaryTeam, true]
-
A.
temporaryIncludesTeam
chosen
Indicates that one entity temporarily includes or has another entity as part of its team for a limited duration or specific period.
-
B.
managedTeam
Indicates that one entity had responsibility for directing, supervising, and coordinating the work of another group or team.
-
C.
exampleTeam
Indicates that an entity is a representative or illustrative member of a particular team or group.
-
D.
team
Indicates that multiple entities are grouped together as a collaborative unit working toward shared goals or tasks.
-
E.
managedTeamFrom
Indicates that one entity led, directed, or supervised a team originating from or based in another specified 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_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 11:05 a.m.