Triple
T33579686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cartier divisor |
E860118
|
entity |
| Predicate | definedLocallyBy |
P4955
|
FINISHED |
| Object | single rational function |
—
|
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: single rational function | Statement: [Cartier divisor, definedLocallyBy, single rational function]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedLocallyBy Context triple: [Cartier divisor, definedLocallyBy, single rational function]
-
A.
representedLocallyBy
chosen
Indicates that an entity is expressed, implemented, or instantiated in a specific local form or representation by another entity.
-
B.
localityOf
Indicates that one entity is the specific place, area, or locality in which another entity is situated or occurs.
-
C.
isLocalTo
Indicates that one entity is geographically or contextually situated near, or within the same local area or scope as, another entity.
-
D.
definesLocation
Indicates that one entity specifies or establishes the spatial or geographic position of another entity.
-
E.
localizedIn
Indicates that one entity is situated, confined, or occurs within a specific region, area, or context defined by 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: May 1, 2026, 1:40 a.m.