Triple
T37860567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | product logarithm |
E944313
|
entity |
| Predicate | hasBranchPoint |
P70435
|
FINISHED |
| Object | z = -1/e |
—
|
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: z = -1/e | Statement: [product logarithm, hasBranchPoint, z = -1/e]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBranchPoint Context triple: [product logarithm, hasBranchPoint, z = -1/e]
-
A.
branchPoint
chosen
Indicates a point in a process, structure, or path where a single preceding element splits into two or more alternative continuations or options.
-
B.
hasBranches
Indicates that an entity extends into multiple subordinate parts or offshoots, like limbs, divisions, or sections stemming from a main source.
-
C.
hasBranchDesignation
Indicates that an entity is assigned a specific branch identifier or designation within a larger organizational or structural system.
-
D.
hasTwoBranches
Indicates that the related entity is divided into or composed of exactly two distinct branches.
-
E.
hasBranchCharacteristic
Indicates that a branch of an entity possesses a specified characteristic or 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:19 p.m.