Triple
T25433512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domineering |
E637317
|
entity |
| Predicate | hasMathematicalInterest |
P178748
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Domineering, hasMathematicalInterest, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMathematicalInterest Context triple: [Domineering, hasMathematicalInterest, high]
-
A.
hasMathematicalDiscipline
Indicates that one entity is associated with or characterized by a particular branch or field of mathematics.
-
B.
hasMathematicalProperty
Indicates that one entity possesses or exhibits a specific mathematical property or characteristic.
-
C.
supportsMathematicsTopic
Indicates that one entity provides assistance, resources, or reinforcement for understanding or working with a particular mathematics topic.
-
D.
hasScientificInterestIn
Indicates that one entity holds a scientific curiosity, concern, or research focus directed toward another entity.
-
E.
mathematicallyUses
Indicates that one entity employs or applies another entity within a mathematical context, such as in a formula, proof, computation, or theoretical framework.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 21, 2026, 1:59 p.m.