Triple
T30596700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Son of Satan |
E778806
|
entity |
| Predicate | teamUp |
P49939
|
FINISHED |
| Object | Doctor Strange |
—
|
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: Doctor Strange | Statement: [Son of Satan, teamUp, Doctor Strange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamUp Context triple: [Son of Satan, teamUp, Doctor Strange]
-
A.
teamUpWith
chosen
Indicates forming a cooperative partnership or alliance with another entity to work together toward a shared goal.
-
B.
team
Indicates that multiple entities are grouped together as a collaborative unit working toward shared goals or tasks.
-
C.
teamBased
Indicates that an activity, process, or structure is organized around collaboration within a group or team rather than by individuals working independently.
-
D.
teamFunction
Indicates the functional role, purpose, or primary responsibility that a team has within a larger organization or context.
-
E.
teamAction
Indicates an action that is performed collectively by a group functioning as a 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6897fc2e881909e2bd183eb7fddc9 |
completed | May 2, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:24 p.m.