Triple
T13590360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Theory of Corporate Finance |
E324676
|
entity |
| Predicate | usesToolFrom |
P98353
|
FINISHED |
| Object | contract theory |
—
|
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: contract theory | Statement: [The Theory of Corporate Finance, usesToolFrom, contract theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesToolFrom Context triple: [The Theory of Corporate Finance, usesToolFrom, contract theory]
-
A.
usesToolFor
Indicates that an agent employs a specific tool to carry out or facilitate a particular action or purpose.
-
B.
usesToolType
Indicates that an entity performs an action or fulfills a role by employing a specific type or category of tool.
-
C.
usedByTool
Indicates that a particular tool is employed or operated by a specified agent or entity.
-
D.
isToolIn
Indicates that a tool is located within or contained inside a specified space, container, or context.
-
E.
usesToolFromDiscipline
chosen
Indicates that an entity employs a tool, method, or technique that originates from or is characteristic of a particular discipline or field.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb055cc98819091fab597b69e5e3e |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.