Triple
T22090763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonny Burch (Ant-Man and the Wasp) |
E545905
|
entity |
| Predicate | seeksToAcquire |
P139685
|
FINISHED |
| Object | portable quantum lab |
—
|
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: portable quantum lab | Statement: [Sonny Burch (Ant-Man and the Wasp), seeksToAcquire, portable quantum lab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seeksToAcquire Context triple: [Sonny Burch (Ant-Man and the Wasp), seeksToAcquire, portable quantum lab]
-
A.
seeksToObtain
chosen
Indicates an entity’s intention or effort to acquire, gain, or come into possession of another entity or resource.
-
B.
seeksToEnsure
Indicates an intentional effort or action aimed at guaranteeing or securing a particular outcome, condition, or state.
-
C.
seeksToExpand
Indicates an entity’s intention or effort to increase the scope, size, influence, or reach of something.
-
D.
seeksToBuild
Indicates an intention or effort by one entity to create, develop, or establish something.
-
E.
acquisitionTarget
Indicates that one entity is the intended or actual company or asset being acquired by another in a merger or acquisition transaction.
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e53dfc81909858cdad8b09c5fb |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.