Triple
T20811170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikolai |
E512305
|
entity |
| Predicate | supportsCharacterGroup |
P47706
|
FINISHED |
| Object | Task Force 141 operators |
—
|
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: Task Force 141 operators | Statement: [Nikolai, supportsCharacterGroup, Task Force 141 operators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCharacterGroup Context triple: [Nikolai, supportsCharacterGroup, Task Force 141 operators]
-
A.
hasCharacterGroupName
Indicates that an entity is associated with a specific name identifying a group of characters.
-
B.
associatedWithCharacterGroup
chosen
Indicates that an entity has a connection or affiliation with a particular group of characters.
-
C.
supportsGroupType
Indicates that one entity is compatible with or able to support a particular category or type of group.
-
D.
containsCharacter
Indicates that one entity includes a specific character as part of its content or composition.
-
E.
capturesCharacter
Indicates that one entity seizes, traps, or takes control of another character.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d338ac819096d4a33de831609e |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:40 p.m.