Triple
T59018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shannon entropy |
E1168
|
entity |
| Predicate | logarithmBaseDetermines |
P4234
|
FINISHED |
| Object | unit of information |
—
|
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: unit of information | Statement: [Shannon entropy, logarithmBaseDetermines, unit of information]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logarithmBaseDetermines Context triple: [Shannon entropy, logarithmBaseDetermines, unit of information]
-
A.
mainBase
Indicates that one entity serves as the primary or central base or headquarters for another entity.
-
B.
isBaseFor
Indicates that one entity serves as the foundational support, starting point, or underlying basis upon which another entity is built, developed, or depends.
-
C.
levelOnPyramid
Indicates the relative vertical tier or layer that an entity occupies within a pyramid structure.
-
D.
keyFormula
Indicates that a formula serves as the primary or defining expression associated with an entity or relationship.
-
E.
numberOfBasementLevels
Indicates the total count of basement levels associated with a given structure or property.
- F. None of above. chosen
Provenance (4 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_69a24a552ef88190a0df287d68c65cba |
completed | Feb. 28, 2026, 1:52 a.m. |
| NER | Named-entity recognition | batch_69a250e401288190ba12322c9c5f07c9 |
completed | Feb. 28, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69a24e9f40908190a2f4a2111469b733 |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a250e2a80881909e5a653260e6f8e0 |
completed | Feb. 28, 2026, 2:20 a.m. |
Created at: Feb. 28, 2026, 1:55 a.m.