Triple
T30334382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loot (for Adventurers) |
E771575
|
entity |
| Predicate | originalContractDeployer |
P89685
|
FINISHED |
| Object | Dom Hofmann |
—
|
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: Dom Hofmann | Statement: [Loot (for Adventurers), originalContractDeployer, Dom Hofmann]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalContractDeployer Context triple: [Loot (for Adventurers), originalContractDeployer, Dom Hofmann]
-
A.
primaryContractSymbol
Indicates that one contract is designated as the main or reference contract symbol associated with another entity or instrument.
-
B.
deployer
chosen
Indicates the agent or entity that carries out the deployment of a system, resource, or artifact.
-
C.
primaryContractor
Indicates that one entity serves as the main responsible contractor for a project, agreement, or work in relation to another entity.
-
D.
deployerType
Indicates the role or category of the agent responsible for deploying or initiating the associated entity or action.
-
E.
initialOwner
Indicates the entity that originally possessed, controlled, or owned another entity before any subsequent transfers or changes in ownership.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a002ae74da08190a4b47e0ff0f7f8fe |
completed | May 10, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_6a0029cc369c81909578e52c4a75ab18 |
completed | May 10, 2026, 6:46 a.m. |
Created at: April 29, 2026, 7:54 p.m.