Triple
T38539445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thor |
E924789
|
entity |
| Predicate | deployedUnderAgreement |
P9252
|
FINISHED |
| Object | Project Emily |
—
|
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: Project Emily | Statement: [Thor, deployedUnderAgreement, Project Emily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deployedUnderAgreement Context triple: [Thor, deployedUnderAgreement, Project Emily]
-
A.
formedByAgreementWith
Indicates that something comes into existence or is established as a direct result of a formal agreement between parties.
-
B.
basedOnAgreementWith
chosen
Indicates that something exists, is done, or is determined on the basis of a prior agreement or accord between the involved parties.
-
C.
implementsAgreementThrough
Indicates that one entity fulfills or carries out the terms of an agreement by means of, or via the mechanisms provided by, another entity.
-
D.
implementsAgreementWith
Indicates that one party carries out or fulfills the terms of an agreement made with another party.
-
E.
involvedAgreement
Indicates that an entity participates in, is a party to, or is otherwise associated with a specific agreement or contract.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd2e930608190b2b2af0d4753d7f0 |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f81cbc8190b4fd3bfc3106c1f3 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.