Triple
T2683155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | spacetime manifold |
E57420
|
entity |
| Predicate | hasLocalProperty |
P23698
|
FINISHED |
| Object | locally Minkowskian |
—
|
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: locally Minkowskian | Statement: [spacetime manifold, hasLocalProperty, locally Minkowskian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalProperty Context triple: [spacetime manifold, hasLocalProperty, locally Minkowskian]
-
A.
haveProperty
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
B.
hasLocalName
Indicates that an entity is known by a specific name or designation within a particular local language, script, or regional context.
-
C.
hasLocalNameFor
Indicates that one entity serves as the local or context-specific name or label used to refer to another entity.
-
D.
hasMappingProperty
Indicates that there exists a defined correspondence or association between elements of one set, structure, or representation and elements of another.
-
E.
hasPropertyType
Indicates that an entity possesses or is associated with a specific type or category of property.
- 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9d602848190b638e417e710a555 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.