Triple
T38260704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brenier map |
E1017920
|
entity |
| Predicate | isDefinedUnder |
P96505
|
FINISHED |
| Object | quadratic cost |
—
|
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: quadratic cost | Statement: [Brenier map, isDefinedUnder, quadratic cost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDefinedUnder Context triple: [Brenier map, isDefinedUnder, quadratic cost]
-
A.
areDefinedIn
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
B.
wasDefinedBy
Indicates that something was formally specified, described, or established by a particular agent, source, or defining entity.
-
C.
canBeDefinedFor
chosen
Indicates that a certain concept, operation, or property is applicable to and can be meaningfully specified for a given entity or set of entities.
-
D.
baseDefinedBy
Indicates that something’s foundational properties, structure, or interpretation are determined or specified by a particular base or underlying system.
-
E.
endDefinedBy
Indicates that the termination or boundary of one entity is determined, specified, or constrained by another entity.
- 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.