Triple
T37860545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | product logarithm |
E944313
|
entity |
| Predicate | realBranches |
P189289
|
FINISHED |
| Object | W_0 on [-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: W_0 on [-1/e,∞) | Statement: [product logarithm, realBranches, W_0 on [-1/e,∞)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realBranches Context triple: [product logarithm, realBranches, W_0 on [-1/e,∞)]
-
A.
realBranchesInterval
chosen
Indicates that the real-valued branches of a function or structure are defined, valid, or considered within a specified interval.
-
B.
branchesFrom
Indicates that one entity originates or diverges from another as a subordinate or offshoot path, structure, or lineage.
-
C.
representedBranch
Indicates that one entity serves as a representative or proxy for a particular branch of another entity or organization.
-
D.
parentBranch
Indicates that one branch serves as the direct ancestor or source from which another branch originates or is derived.
-
E.
hasBranches
Indicates that an entity extends into multiple subordinate parts or offshoots, like limbs, divisions, or sections stemming from a main source.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.