Triple
T5446365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carathéodory metric |
E122257
|
entity |
| Predicate | canDegenerateOn |
P64356
|
FINISHED |
| Object | non-hyperbolic domains |
—
|
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: non-hyperbolic domains | Statement: [Carathéodory metric, canDegenerateOn, non-hyperbolic domains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canDegenerateOn Context triple: [Carathéodory metric, canDegenerateOn, non-hyperbolic domains]
-
A.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
B.
canElect
Indicates that one entity has the authority or ability to choose another entity for a position, role, or office through an election process.
-
C.
canMake
Indicates that one entity has the ability or capacity to create, produce, or assemble another entity.
-
D.
canDeclare
Indicates that one entity has the authority or ability to formally declare or announce something about another entity or situation.
-
E.
canBeDisabledOn
Indicates that a feature, function, or capability has the property that it can be turned off or deactivated when applied to the referenced entity.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd95bd53f48190a03144beb290f2cb |
completed | March 20, 2026, 6:45 p.m. |
Created at: March 20, 2026, 2:07 p.m.