Triple
T34625571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton’s compactness theorem for Ricci flow |
E889125
|
entity |
| Predicate | technicalTool |
P28572
|
FINISHED |
| Object | Arzelà–Ascoli type arguments for tensor fields |
—
|
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: Arzelà–Ascoli type arguments for tensor fields | Statement: [Hamilton’s compactness theorem for Ricci flow, technicalTool, Arzelà–Ascoli type arguments for tensor fields]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technicalTool Context triple: [Hamilton’s compactness theorem for Ricci flow, technicalTool, Arzelà–Ascoli type arguments for tensor fields]
-
A.
toolOrProduct
Indicates that one entity is used as a tool or produced as a product in relation to another entity or activity.
-
B.
toolIn
chosen
Indicates that one entity is a tool or instrument used in or associated with another entity or context.
-
C.
toolType
Indicates the specific kind or category of tool associated with an entity.
-
D.
toolDescribed
Indicates that one entity provides a description or explanation of a tool associated with another entity.
-
E.
toolUsed
Indicates that an action or task is performed using a particular tool as the means or instrument.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.