Triple
T37860541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | product logarithm |
E944313
|
entity |
| Predicate | branchIndexNotation |
P52369
|
FINISHED |
| Object | W_k(z) |
—
|
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_k(z) | Statement: [product logarithm, branchIndexNotation, W_k(z)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchIndexNotation Context triple: [product logarithm, branchIndexNotation, W_k(z)]
-
A.
offsetNotation
chosen
Indicates that one representation specifies how far and in what way another representation is shifted or displaced from a reference point or baseline.
-
B.
branchPosition
Indicates the relative location or placement of something along a branch.
-
C.
branchStructure
Indicates how the parts of a branching system are organized and connected relative to one another.
-
D.
branchPoint
Indicates a point in a process, structure, or path where a single preceding element splits into two or more alternative continuations or options.
-
E.
branchComposition
Indicates that one branch or subdivision is structurally or functionally composed of, or made up from, another entity or set of entities.
- 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_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.