Triple
T17884794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wetworks |
E447172
|
entity |
| Predicate | hasTeamBase |
P129136
|
FINISHED |
| Object | various covert military facilities |
—
|
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: various covert military facilities | Statement: [Wetworks, hasTeamBase, various covert military facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTeamBase Context triple: [Wetworks, hasTeamBase, various covert military facilities]
-
A.
teamBase
Indicates that one entity serves as the primary or foundational team associated with another entity.
-
B.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
-
C.
hasTeamStadium
Indicates that a sports team is associated with or plays its home games at a particular stadium.
-
D.
hasSubteam
Indicates that one team is a subordinate or component team within another, larger team.
-
E.
stateTeamOf
Indicates that one entity is the official team representing a particular state associated with another entity.
- F. None of above. chosen
Provenance (4 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49c123748819091bf46178105079b |
completed | April 19, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:18 a.m.