Triple
T37729643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian government (Marvel Universe) |
E940120
|
entity |
| Predicate | hasSecretProgram |
P202620
|
FINISHED |
| Object | Weapon X Program |
—
|
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: Weapon X Program | Statement: [Canadian government (Marvel Universe), hasSecretProgram, Weapon X Program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecretProgram Context triple: [Canadian government (Marvel Universe), hasSecretProgram, Weapon X Program]
-
A.
hasSecretArea
Indicates that an entity contains or is associated with a hidden or restricted area not normally accessible or visible.
-
B.
hasFamilySecret
Indicates that there exists a confidential or hidden matter shared within or pertaining to a family relationship.
-
C.
hasSecretLevel
Indicates that an entity is associated with a particular secrecy or security classification level.
-
D.
hasSecretFacility
Indicates that an entity possesses or controls a hidden or undisclosed facility.
-
E.
hasSecretExit
Indicates that something includes or is connected to a hidden or concealed way out.
- 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00a15604fc8190b1c280794960f3a4 |
completed | May 10, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_6a00a0f7e77881909ac85755ab0e6329 |
completed | May 10, 2026, 3:15 p.m. |
| PDg | Predicate description generation | batch_6a00a154c3b0819088de3f22f3f81040 |
completed | May 10, 2026, 3:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.