Triple
T22328568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fubini–Study form |
E551964
|
entity |
| Predicate | locallyGivenBy |
P4955
|
FINISHED |
| Object | i∂∂̄ log(∑|z_i|^2) |
—
|
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: i∂∂̄ log(∑|z_i|^2) | Statement: [Fubini–Study form, locallyGivenBy, i∂∂̄ log(∑|z_i|^2)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locallyGivenBy Context triple: [Fubini–Study form, locallyGivenBy, i∂∂̄ log(∑|z_i|^2)]
-
A.
representedLocallyBy
chosen
Indicates that an entity is expressed, implemented, or instantiated in a specific local form or representation by another entity.
-
B.
localityCondition
Indicates a spatial or contextual constraint specifying where or under what local conditions a relationship, event, or property holds.
-
C.
formsLocalityWith
Indicates that two or more entities together constitute or define a specific locality or local area.
-
D.
isLocalTo
Indicates that one entity is geographically or contextually situated near, or within the same local area or scope as, another entity.
-
E.
localizationBy
Indicates a relationship where one entity determines, specifies, or constrains the spatial or contextual location of 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15769fdb48190b84e0c019ab63579 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.