Triple
T12630325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 14 Intelligence Company |
E301621
|
entity |
| Predicate | usedCoverIdentities |
P47547
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [14 Intelligence Company, usedCoverIdentities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedCoverIdentities Context triple: [14 Intelligence Company, usedCoverIdentities, yes]
-
A.
usedBySuperheroIdentity
Indicates that a particular item, tool, or resource is utilized by a given superhero identity.
-
B.
coverIdentities
chosen
Indicates that one entity conceals, masks, or protects the true identities of one or more other entities.
-
C.
hasSecretIdentity
Indicates that an entity possesses an alternate, hidden identity that is not publicly known.
-
D.
appearsInIdentity
Indicates that an entity is featured, referenced, or plays a role within a particular identity or identity-related context.
-
E.
hasSuperheroIdentityType
Indicates the type or category of a superhero identity associated with an entity (e.g., secret, public, dual).
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:15 p.m.