Triple
T34419051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GAGA |
E883477
|
entity |
| Predicate | establishesConnectionBetween |
P37306
|
FINISHED |
| Object | algebraic geometry |
—
|
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: algebraic geometry | Statement: [GAGA, establishesConnectionBetween, algebraic geometry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishesConnectionBetween Context triple: [GAGA, establishesConnectionBetween, algebraic geometry]
-
A.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
B.
connectionTo
chosen
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
C.
connectsViaCanal
Indicates that one entity is linked or joined to another by means of a canal.
-
D.
connectsPreviouslySeparateSystems
Indicates that an entity establishes a link or integration between systems that were previously independent or isolated from one another.
-
E.
ridgeConnection
Indicates a structural relationship where one ridge is connected or linked to another ridge, forming a continuous or associated ridge feature.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 1, 2026, 2 a.m.