Triple
T21145339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kobayashi metric |
E521038
|
entity |
| Predicate | isContractedBy |
P143046
|
FINISHED |
| Object | holomorphic self-maps |
—
|
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: holomorphic self-maps | Statement: [Kobayashi metric, isContractedBy, holomorphic self-maps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isContractedBy Context triple: [Kobayashi metric, isContractedBy, holomorphic self-maps]
-
A.
hasContractWith
Indicates that one entity is bound by a formal contract or agreement with another entity.
-
B.
mayContractWith
Indicates that one entity is permitted or authorized to enter into a contractual agreement with another entity.
-
C.
hasExclusiveContractFor
Indicates that one party holds sole contractual rights to provide, use, or represent a specific product, service, or opportunity, excluding all other potential counterparties.
-
D.
canBeContractedOutOf
Indicates that a right, obligation, or condition may be removed, waived, or excluded through a contractual agreement between the parties.
-
E.
hasContractStyle
Indicates that one entity is associated with or characterized by a particular contract style or contractual format.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723fcdb7c8190ae04d6ad9dff3187 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 2:58 p.m.